You are not logged in.
The uname request was only for daren_k who probably has an entirely different problem.
To me this looks like the kernel forgot to init a variable and relied on the memory being cleared by the bootloader - what doesn't happen w/ syslinux.
Offline
Test patch from https://bugzilla.kernel.org/show_bug.cgi?id=216387#c3
https://drive.google.com/file/d/1CM4WRZ … sp=sharing linux-5.19.2.arch1-2.4-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1BKvrgH … sp=sharing linux-headers-5.19.2.arch1-2.4-x86_64.pkg.tar.zst
That one boots up fine.
Offline
The fix has been formalized in https://lore.kernel.org/all/YwUKNX6USrBSrSa6@zn.tnic/ and is tagged for stable.
Offline
what is strange on my desktop I have boot up with 5.19.3-arch1-1 which is from official arch repo and syslinux 6.04.pre2.r11.gbf6db5b4-3
Offline
Test patch from https://bugzilla.kernel.org/show_bug.cgi?id=216387#c3
https://drive.google.com/file/d/1CM4WRZ … sp=sharing linux-5.19.2.arch1-2.4-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1BKvrgH … sp=sharing linux-headers-5.19.2.arch1-2.4-x86_64.pkg.tar.zst
[...]
The kernel works. I will also confirm that in the upstream bug report. Thanks for all the great work loqs.
Offline
Hello,
Is this fixed for you with linux 5.19.4.arch1-1 ?
I've similarly problem but I still bootloop with this new kernel. Maybe it's not exactly the same problem...
Offline
Don't think so. It's not upstream yet, and there are no patches applied in the arch package.
Offline
I have the same issue. Upgraded from 5.18.9 to 5.19.2 and reboots when the before mentioned 3 lines of text is displayed:
Loading intramfs-linux.img ok
Loading intel-ucode.img ok
Loading vmlinuz.linux okI solved the issue by downgrading to 5.18.9, but a solution could be nice. Otherwiser, I hope a new kernel release solves the problem (a lazy approach I know).
Just for info. I solved the issue by changing bootloader from Syslinux to GRUB. Then I successfully upgraded to 5.19.4.
Offline
Just for info. I solved the issue by changing bootloader from Syslinux to GRUB. Then I successfully upgraded to 5.19.4.
Doesn't guarantee to work - i have grub on the affected (UEFI) systems, and it still fails.
Offline
The fix is in linux stable tree now: https://git.kernel.org/pub/scm/linux/ke … isc.h#n137
So it should be resolved in 5.19.6 when that gets released.
Offline
Indeed it is. Running the archlinux kernel 5.19.6-arch1-1 and am able to boot again. I am not the OP, but the thread could be marked as resolved now.
Offline
Also not the OP, but I can confirm that the latest kernel, 5.19.7-zen2-1-zen, is booting just fine again.
Offline
Same problem as everyone here on an Asus N76VM laptop, with multiple lvm partitions.
Instant reboot after syslinux tries to start the kernel.
Downgrading the linux kernel and headers to 5.18.6 fixed the issue.
I think I have the same problem here, it’s boot looping but every time into the setup utility, I’m a newbie so how do I downgrade it?
Offline
Downgrading packages. Please note the issue covered by this thread was fixed in 5.19.6.
Offline