Bug 1965859 - When booting from a kernel built with dracut 054-12.git20210521.fc34, the system is unusable after boot
Summary: When booting from a kernel built with dracut 054-12.git20210521.fc34, the sys...
Status: CLOSED DUPLICATE of bug 1964879
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 34
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-31 01:53 UTC by John Apple II
Modified: 2021-06-10 00:50 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-06-10 00:50:15 UTC
Type: Bug

Attachments (Terms of Use)
Boot of newer kernel using dracut 054-12.git20210521.fc34 (318.53 KB, text/plain)
2021-05-31 01:53 UTC, John Apple II
no flags Details

Description John Apple II 2021-05-31 01:53:30 UTC
Created attachment 1788117 [details]
Boot of newer kernel using dracut 054-12.git20210521.fc34

Description of problem:

When I boot from a kernel built with the current version of dracut, the system is unusable.  Running a Lenovo T590.

Broken dracut is version 054-12.git20210521.fc34

Downgrading to 053-4.fc34 and rebuilding using `sudo dracut --force` and rebooting causes the system to work without issue

Version-Release number of selected component (if applicable): dracut version 054-12.git20210521.fc34

How reproducible:
Upgrade to dracut 054-12.git20210521.fc34 and dependencies, built the initramfs using dracut, and then reboot.

Steps to Reproduce:
1. Upgrade system with dracut, with a new kernel which builds with the newer version of dracut
2. Reboot into the new kernel
3. Boot will hang at Switch Root
4. systemd-logind, NetworkManager will fail with errors related to an inability to connect to DBus.
5. Reboot into an older kernel built with dracut 053-4.fc34
6. Downgrading dracut to 053-4.fc34
7. Rebuild the newer-but-failing kernel with the older dracut
8. Reboot into the same newer-but-failing kernel results in a completely successful boot with all DBus, systemd-logind, and NetworkManager functions working - including no hang at Switch Root.

Actual results:

Boot fails with errors in systemd-logind and NetworkManager failing to start complaining about DBus.

Expected results:

Boot succeeds without issues in systemd-logind and NetworkManager or DBus.

Additional info:

Attaching boot information using a kernel built with dracut 054-12.git20210521.fc34 as jctlmesgfc34testing.txt

Comment 1 Andreas 2021-05-31 07:38:31 UTC
I am experiencing the same bug on a Dell Latitude 7400.

Comment 2 Radu Adam 2021-05-31 13:06:49 UTC
Somewhat related - I think - this is what I'm experiencing:

Booting with kernel 5.12.7-300/dracut v054-12.git201210521 my system is semi-unusable: dbus-broker.service is throwing errors and other services depending on dbus are not started/not running (NetworkManager, systemd-resolved). After booting I can log in and restart these services and everything is running fine. But after rebooting I have the same issues.

Downgrading to dracut 053-4 and rebuilding the initramfs doesn't fix the problem on kernel 5.12.7-300, but it helps with 5.11.12-300.

I'm running Fedora 34 on a Thinkpad T480 with Intel i7-8650U CPU.

Comment 3 rtqate 2021-06-02 20:38:17 UTC
5.12.8-300.fc34.x86_64 plus the latest updates (in short, today's "sudo dnf update") fixed this for my Dell laptop, finally (12.5, 12.6, and 12.7 were not working, to varying extents). Thanks!

Comment 4 rtqate 2021-06-03 04:21:37 UTC
I reacted too early - 5.12.8-300.fc34.x86_64  still has problems (VS Code and VIM are not working).

Comment 5 Oleg Girko 2021-06-04 03:02:56 UTC
Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1964879

Comment 6 Oleg Girko 2021-06-04 03:07:32 UTC
One more related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1965585

Comment 7 rtqate 2021-06-08 20:11:44 UTC
Same issue (freeze) on kernel-core-5.12.9-300.fc34.x86_64

Comment 8 Adam Williamson 2021-06-10 00:50:15 UTC

*** This bug has been marked as a duplicate of bug 1964879 ***

Note You need to log in before you can comment on or make changes to this bug.