1. Please describe the problem: I just upgraded my Fedora 34 system to kernel 5.12.13, and the system does not boot. If I choose the previous kernel 5.12.12, then the system boots properly 2. What is the Version-Release number of the kernel: 5.12.13 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : The problem first appeared in 5.12.13. I had no problems with the previous kernel 5.12.12. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: I simply did a "dnf upgrade", and found that the system failed to reboot. I'll add an attachement showing a normal boot, and a screen photo of where it fails. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I have not tried a rawhide kernel. 6. Are you running any modules that not shipped with directly Fedora's kernel?: I am using the proprietary nvidia display driver, because the nouveau driver randomly crashes. I've never had a problem with the proprietary nvidia driver. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. I can attach a good boot log, but I cannot attach a bad boot log, because the kernel doesn't get far enough to log anything. But I will attach a photo showing where it stops.
Created attachment 1796430 [details] This image shows a failed boot The failure happens right after the disks are recognized.
Created attachment 1796431 [details] This log file shows a GOOD boot Like I said above, I don't seem to be able to get a log of a bad boot, apparently because the boot process hangs too early to log anything to disk. If there is some way to get more info, please let me know and I'll try...
The next message I'd expect to see on the console after the "Attached SCSI disk" message would be "initrd-switch-root.service: Deactivated successfully", so that is where things seem to break. I tried doing a "dnf reinstall" of all the kernel packages, but that didn't help.
This looks like the same dracut/dbus bug hitting a lot of people, it has nothing to do with the kernel, it just happens that the initramfs gets created when the kernel is installed. Workarounds include downgrading to dracut 0.53 or modifying dbus start up as mentioned in the bug I am duping this to. *** This bug has been marked as a duplicate of bug 1976653 ***
I applied the dbus startup patch, and was able to boot 5.12.13-300. Thanks for the help!