Bug 1782879
| Summary: | 30 secons boot delay: a stop job is running for udev | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miguel Angel <mikioma> | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 31 | CC: | keller1976, lnykryn, mikioma, msekleta, rhbugs, ssahani, s, systemd-maint, xose.vazquez, zbyszek | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | systemd-243.5-1.fc31 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-12-19 16:24:02 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: |
|
||||||
|
Description
Miguel Angel
2019-12-12 14:42:02 UTC
My apologies, I meant Arch Linux, running systemd-244-1 does NOT have such delay. I observe the same thing with my desktop PC. Using an Asus mother board with Xenon CPU and Nvidia GPU with Nvidia driver from rpmfusion. This only started recently. Earlier versions of F31 had no problems. I don't know if it is related, but the Plymouth boot screen stopped showing at the same time. Now I only get the black screen until SDDM starts. systemd-243.5-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-29767c1981 FEDORA-2019-29767c1981 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-29767c1981 Updating to systemd-243.5-1 did not solve the issue for me. *** Bug 1781329 has been marked as a duplicate of this bug. *** systemd-243.5-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. Problems still persist. Can somebody who is experiencing this attach an updated boot log (like in comment #0)? Apologies for the noise. I noticed that the systemd in initramfs was still on the old version. I ran "sudo dracut -f" to rebuild initramfs, and now the problem is solved on boot for me (should a systemd update trigger an initramfs rebuild automatically?). Thanks for the fix. Ha, I was suspecting that!
> should a systemd update trigger an initramfs rebuild automatically?
No. Systemd is only one of the things in the initramfs. In principle we could rebuild
the initramfs every time a package that has files that end up in the initramfs gets
updated, but that'd be very unwieldy, since rebuilding of the initramfs is slow,
and we don't have a list of such packages. Also, people have more than one initramfs,
and in principle we would have to rebuild all of them. Apart from being slow, rebuilding
of the initramfs can easily go wrong... In the end, we currently only build the
initramfs on kernel installation and never touch it afterwards.
Very much the same here: Simply updating the package did not solve the issue, but after rebuilding initramfs Thanks so much for the fix! |