Bug 1614773

Summary:	Getting a few minute delay during shutdown/reboot and on start of Fedora 28
Product:	[Fedora] Fedora	Reporter:	naaa <bareye4583>
Component:	udev	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	extras-orphan, johannespfau, jonathan
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:	2018-08-10 22:33: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:

Description naaa 2018-08-10 12:04:55 UTC

Description of problem: Getting a few minute delay during shutdown/reboot and on start of Fedora 28 immediately after latest BIOS update on AMD Ryzen platform. Tried several setting changes in BIOS with no change.

Version-Release number of selected component (if applicable): udevadm --version 238

How reproducible:

Steps to Reproduce:
1. Update to AMI BIOS 7A38vAD using AGESA Code 1.0.0.4C
2. Boot to Fedora
3.

Actual results: Shutdown/Reboot:
Systemd-udevd[601]: giving up waiting for workers to finish
Systemd-udevd[601]: event loop failed: connection timed out

Start:
A start job is running for Monitoring of lvm2 mirr… using dmeventd or progress polling
A start job is running for Udev wait for complete device initialization

Expected results: No wait

Additional info: Fedora 28 fully updated using current Kernel 4.17.12-200.fc28.x86_64

Using "$ systemctl mask systemd-udev-settle" works around the problem with startup but doesn't fix the wait during shutdown/reboot.

I would think that this shouldn't be happening (and disabling stuff isn't a correct fix) but don't know which side of the line it falls on as a bug. Nothing else happened except for a BIOS update and since the BIOS change log is terribly crappy, no idea what the differences are between this one and the last.

Comment 1 Johannes Pfau 2018-08-10 18:10:19 UTC

This seems to be the same bug: https://bugzilla.redhat.com/show_bug.cgi?id=1608242

Comment 2 naaa 2018-08-10 22:30:03 UTC

I agree, that does sound just like it. There's why I rarely make bug reports lol. Sorry about that =)

Comment 3 naaa 2018-08-10 22:33:25 UTC


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