Bugzilla – Bug 1221722
Can not boot with 64K pages on arm64
Last modified: 2024-03-21 09:06:22 UTC
From bugzilla https://bugzilla.suse.com/show_bug.cgi?id=1220587 kernel kernel-64kb-6.4.0-150600.1.1.gf0903b0.aarch64.rpm on arm64 cannot boot and I see this at console [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Forward Password R…s to Plymouth Director[ 67.112624][ T1488] nvme0n1: p1 p2 p3 p4 y Watch. [ OK ] Reached target Path Units. [ OK ] Reached target Basic System. [ 67.133478][ T2516] BTRFS: device fsid 78f87e9f-62d9-4cd1-8549-8b532769818e devid 1 transid 17982 /dev/nvme0n1p2 scanned by (udev-worker) (2516) [ OK ] Found device SAMSUNG MZ1L21T9HCLS-00A07 1. [ OK ] Found device SAMSUNG MZ1L21T9HCLS-00A07 2. [ OK ] Reached target Initrd Root Device. [ 67.219677][ T1894] usb 1-4: new high-speed USB device number 2 using xhci_hcd [ 67.382301][ T1894] usb 1-4: New USB device found, idVendor=1d6b, idProduct=0107, bcdDevice= 1.00 [ 67.391382][ T1894] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 67.399394][ T1894] usb 1-4: Product: USB Virtual Hub [ 67.404560][ T1894] usb 1-4: Manufacturer: Aspeed [ 67.409373][ T1894] usb 1-4: SerialNumber: 00000000 [ 67.418464][ T1894] hub 1-4:1.0: USB hub found [ 67.423300][ T1894] hub 1-4:1.0: 7 ports detected [ OK ] Finished dracut initqueue hook. [ OK ] Reached target Preparation for Remote File Systems. [ OK ] Reached target Remote File Systems. Starting File System Check…62d9-4cd1-8549-8b532769818e... [ OK ] Finished File System Check…f-62d9-4cd1-8549-8b532769818e. [ 67.509488][ T2757] BTRFS info (device nvme0n1p2): using crc32c (crc32c-generic) checksum algorithm Mounting /sysroot[ 67.520888][ T2757] BTRFS info (device nvme0n1p2): disk space caching is enabled ... [ 67.531283][ T2757] BTRFS warning (device nvme0n1p2): v1 space cache is not supported for page size 65536 with sectorsize 4096 [ 67.543502][ T2757] BTRFS error (device nvme0n1p2): open_ctree failed [FAILED] Failed to mount /sysroot. See 'systemctl status sysroot.mount' for details. [DEPEND] Dependency failed for Initrd Root File System. [DEPEND] Dependency failed for Relo…figuration from the Real Root. [ OK ] Stopped target Basic System. [ OK ] Reached target Initrd File Systems. [ OK ] Stopped target System Initialization. [ OK ] Stopped dracut initqueue hook. [ OK ] Stopped dracut pre-udev hook. [ OK ] Stopped dracut cmdline hook. [ OK ] Stopped dracut ask for additional cmdline parameters. [ OK ] Started EmergencGive root password for maintenance (or press Control-D to continue): [ 67.719677][ T1894] usb 1-4.1: new high-speed USB device number 3 using xhci_hcd [ 67.831061][ T1894] usb 1-4.1: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 6.01 [ 67.840317][ T1894] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 67.848506][ T1894] usb 1-4.1: Product: RNDIS/Ethernet Gadget [ 67.854385][ T1894] usb 1-4.1: Manufacturer: Linux 6.1.15-47de273 with aspeed_vhub
Can you still mount this disk when you boot with SLE15-SP5 64kb kernel?
(In reply to Takashi Iwai from comment #2) > Can you still mount this disk when you boot with SLE15-SP5 64kb kernel? I can boot with this kernel 5.14.21-150500.55.52-64kb the same system I attempted to use kernel-64kb-6.4.0-150600.1.1.gf0903b0.
in another system that we installed SLES15 sp6 iso and then installed kernel-64kb-6.4.0-150600.1.1.gf0903b0.aarch64.rpm I was able to boot with this kernel. The system that I encountered this issue, I installed first sles 15 sp5 iso and then installed this kernel rpm. Let me see what happens to the same system if I install sles 15 sp6 beta iso and then this kernel rpm. Attaching the dmesg when it booted with another system.
Created attachment 873644 [details] dmesg of system that booted ok
I confirmed that at the same system I saw this issue, if I use the sles 15 sp6 beta iso and then install kernel rpm kernel-64kb-6.4.0-150600.1.1.gf0903b0.aarch64.rpm it boots ok. will attach dmesg just in case.
Created attachment 873645 [details] dmesg at same system I hit the issue with Sles15 sp6 iso installed
Carol, this is test kernel which could fail.
For completeness, the message says that it did not mount because of v1 cache. If you mount the filesystem with options clear_cache,space_cache=v2, it should work.
(In reply to Goldwyn Rodrigues from comment #9) > For completeness, the message says that it did not mount because of v1 > cache. If you mount the filesystem with options clear_cache,space_cache=v2, > it should work. It still weird that if I have the system installed with SLES 15 sp5 and put the test kernel it will fail and if I put the test kernel with sles 15 sp6 worked ok. I did not change anything in the mount options.
*** Bug 1221721 has been marked as a duplicate of this bug. ***