Bug 1789906

Summary: systemd-udevd needlessly waits
Product: [Fedora] Fedora Reporter: udo <udovdh>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: lnykryn, msekleta, ngaywood, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 18:09:59 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 Flags
good boot
none
bad boot none

Description udo 2020-01-10 16:55:59 UTC 
Description of problem:
Sometimes the system boots quickly, sometimes systemd-udevd finds it necessary to wait up to 2 minutes and 58 seconds for no good reason.
Killing it before that time continues the boot with no issue.


Version-Release number of selected component (if applicable):
systemd-udev-243.5-1.fc31.x86_64

How reproducible:
Boot fedora.

Actual results:
Slow boot due to systemd-udevd

Expected results:
Quick boot.

Additional info:
X570 AORUS PRO with latest BIOS with AMD Ryzen 5 3400G with Radeon Vega Graphics running fedora 31, git mesa, kernel.org, etc.
Comment 1 udo 2020-10-22 14:16:17 UTC 
Fedora 32 now
Comment 2 Zbigniew Jędrzejewski-Szmek 2020-10-22 18:24:08 UTC 
Sorry for the slow reply. Can you attach logs from a successful and failed boot?
Comment 3 udo 2020-10-23 02:54:25 UTC 
Created attachment 1723657 [details]
good boot
Comment 4 udo 2020-10-23 02:56:51 UTC 
Created attachment 1723658 [details]
bad boot

when udev-settle waits I usually kill it with ctrl-alt-prtsc-e.
Comment 5 udo 2020-10-23 02:57:23 UTC 
As soon as it happens in fedora 32/kernel 5.9 I will update the bug.
Comment 6 Zbigniew Jędrzejewski-Szmek 2020-10-23 06:01:10 UTC 
Hmm, that's just dmesg, but the issue is in userspace, so this doesn't tell much. Can you attach
'journalctl -b --no-hostname -o short-monotonic'?
Comment 7 udo 2020-10-23 06:03:32 UTC 
When I see the issue I will.
Comment 8 Fedora Program Management 2021-04-29 16:01:56 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 9 Zbigniew Jędrzejewski-Szmek 2021-05-18 18:09:59 UTC 
I'll assume this was the same issue and close this as duplicate.

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