Bug 1866367
| Summary: | Bootup taking 2 hours | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bret Joseph <bretjoseph> | ||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 33 | CC: | acaringi, airlied, bskeggs, bugzilla, filbranden, flepied, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, lgoncalv, linville, lnykryn, masami256, mchehab, mjg59, msekleta, ssahani, s, steved, systemd-maint, zbyszek, z | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-08-31 00:41:25 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1710581 [details]
dmesg log
Seems to have been fixed after systemd update but now that kernel will not login I believe that your initial assessment that this is a systemd issue was correct, I'm seeing this too and for me downgrading systemd to the latest 245.7-1 build from F32 fixes things. Are you saying that if you boot an older kernel things work fine ? I tried booting a 5.7.12 kernel but that had the same issue for me. I've filed bug 1867930 against systemd for this. As I mentioned there I added "systemd.debug-shell=1" to my kernel commandline to get a debug-shell and vt9, I also had to boot into textmode (at 3 to the kernel commandline) to debug things. Then on the debug-shell if you run "top" you will see systemd and logind and dbus-broker taking up a lot of CPU, at least if you are really hitting the same issue. Note for me top would hang. I had to CTRL+C it and then edit /etc/nsswitch.conf and remove "systemd" from the group and passwd lines to make top not hang. This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33. Hmm, both dmesg and boot.log are not very useful. Can you attach something like 'journalctl -o short-unix --no-hostname -b' ? Its fixed now. The login issue I might have caused when I booted with selinux=0 Sounds like we're not sure what the problem was, but it's also not a problem anymore? If I've got that wrong, or it comes back, please reopen. |
Created attachment 1710506 [details] Boot Log The kernel vmlinuz-5.8.0-1.fc33.x86_64 takes 2 Hours to boot up either to reach multiuser or graphical target If I upgrade to rawhide from 32 or If I use fresh netinstall iso install minimal or workstation Boot to multiuser or graphical desktop This fresh install kernel will reboot fine only if I dont install stuff Install a couple of applications chromium, gtk4 and other simple gnome-stuff Other wise I have to wait 2 hours exactly then it shows login screen