My Fedora 40 system won’t boot with any kernel over 6.8.10.
I’ve had this problem for about a month now and have been putting it off, as I haven’t really been using my computer recently, but it needs to be addressed.
I’m running a Fedora 40 KDE 6 distro, which was upgraded from Fedora 39. It’s been working pretty well for the half year I’ve been using it but recently I’ve encountered an issue. About a month ago, after upgrading my system to kernel 6.8.10, my system started to hang while in boot.
usb 1-10 device descriptor read/64, error -71 [ OK ] Started plymouth-start.service - Show Plymouth Boot Screen [ OK ] Started systemd-ask-password-plymoūquests to Plymouth Directory Watch [ OK ] Reached target paths.target - Path Units. [ OK ] Found device dev-disk-by\x2duuid-dūsung SSD 970 EVO Plus 500GB fedora. [ OK ] Reached target initrd-root-device.target - Initrd Root Device. [ *** ] Job dev-mapper-cl\x2dswap.device/start running (xxs / no limit)
Fortunately Fedora saves the previous 2 kernels versions and I was able to boot into my computer using Kernel 6.8.9. When I went to check what was wrong I noticed that with kernel 6.8.10 it always hangs at this part of the boot process.
[ *** ] Job dev-mapper-cl\x2dswap.device/start running (xxs / no limit)
I understood that this has something to do with swap but I’m unsure what the issue is exactly. My Fedora install doesn’t have a swap partition, it uses zram. I’m unsure if that’s an issue.
I’ve reinstalled kernel 6.8.10 and it didn’t fix the issue. I’ve also upgraded my machine to use kernel 6.8.11 and see if that would fix anything, but it did nothing, and upgrading to 6.8.12 probably won’t fix anything either. I’ve installed a dnf plugin called versionlock meant to pin certain kernels as to not delete them and have already pinned kernel 6.8.9, but I’d still rather avoid upgrading.
What I really don’t understand is what changed. Why does my system boot successfully in kernel 6.8.9 but fails in 6.8.10. I’ve read that others have had a similar experience with the 6.8.10 kernel on fedora, albeit for different reasons.
If someone can point me to the answers that would be great, but an explanation as to how to read that log and steps I could take to identify and troubleshoot would be just as welcomed.
UPDATE: In my /proc/cmdline I had an argument known called resume=/dev/mapper/cl-swap which was trying to find a swap partition that didn’t exist.
I used the command cat /proc/cmdline to view my boot arguments and then ran the command sudo grubby --remove-args=<resume=UUID=xxx> --update-kernel=ALL where <resume=UUID=xxx was replaced with resume=/dev/mapper/cl-swap.
Thank you [email protected] for linking the thread.
Boot to the previous kernel and run updates until you get a 6.9, or go download and install the rpms yourself.
They pushed a bad patch with 6.8.10 I think? They had to roll it back and push another real quick, but some caching issue still delivered it to a bunch of people. You should on the 6.9 line now anyway as 6.8 is EOL.
Sorry for responding so late I was busy at the moment.
I didn’t fully understand what you meant by " run updates until you get a 6.9"
Also what exactly should I be downloading and installing. The new patched kernel?
When you run 'dnf update ', you want it to say it’s going to install kernel 6.9.X.
Hello I did as you advised and my system installed the kernel 6.9.4
Nothing really changed. Still hung at that same exact spot. Honestly the only thing I’d like right now is to know what
Job dev-mapper-cl\x2dswap/startmeansStill thank you for replying
See if it’s the swap, disable zram and/or add a swap file.
Doesn’t have to be a swap partition, you can create a file, format it as swap and assign it in /etc/fstab.
Btw when you say you don’t have swap do you mean you don’t have regular swap file/partition (because you have zram swap) or you don’t have swap at all?
That is a systems job for finding and mounting swap space on your machine. Is it failing?
This.
This sounds very similar OP: https://discussion.fedoraproject.org/t/solved-boot-hang-job-dev-disk-by-x2uuid-no-limit/119111
Thanks for linking the thread, I spent a whole day looking through fedoraproject threads, don’t know how I missed this one. Again thanks.
deleted by creator
@Doctor_Rex Same here ((
@Doctor_Rex I am asking about this issue on Linux Questions here: https://www.linuxquestions.org/questions/showthread.php?p=6511848#post6511848
Hey I found my solution here https://discussion.fedoraproject.org/t/solved-boot-hang-job-dev-disk-by-x2uuid-no-limit/119111
hope this helps.
Fedora’s curremt kernel version is 6.9 so test with that
Same error
@Doctor_Rex Do you have a thunderbolt device?
“It is a kernel regression problem, introduced in Kernel 6.8.8. Thunderbolt devices, not only external disks, are not correctly initialized.”
Thunderbolt? No.
I have a second sata ssd which I mount as my home partition.
dev-mapper swap…
Any
resumeargument in your boot commands? Try removing them and see what happensIt looks like it is booting fine to me. If you get to systemd the kernel is at least mostly working
@Doctor_Rex What happens when you boot the recovery/rescue kernel, or add the flag
nomodesetto the current kernel? I feel it *is* booting, just not showing anything (so a GUI issue), sadly I’ve seen that before.Thanks for the warning.
This is a specific case.
![[SOLVED] Fedora 40 won't boot with Kernel 6.8.10 or above](https://lemmy.ml/pictrs/image/f8253c7f-5cec-49e9-923a-4933664b2adb.jpeg){kind=link}