http://bugzilla.suse.com/show_bug.cgi?id=1058028 http://bugzilla.suse.com/show_bug.cgi?id=1058028#c9 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(shivasharan.srika | |nteshwara@broadcom.com) --- Comment #9 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Thomas Blume from comment #8)

...

The reason for the BZ was because we feel the 30second wait is too less. There can be many valid scenarios (like more number of controllers, or a large device config) where driver load could be taking more than 30seconds. So we wanted to figure out if there is any tunable (either existing or something new) that can be added to control this.

I guess there is a reason why these 30s are hardcoded. One has to consider that waiting longer for systemd-udevd to exit could delay the system startup as well as the shutdown. We can probably make this tunable but at the moment I'd rather focus on delaying the shutdown of systemd-udevd if there are still drivers loading. I will let you know as soon as I have new findings.

Could you please attach the output of: journalctl -xu systemd-udev-settle.service from the boot journal? -- You are receiving this mail because: You are on the CC list for the bug.