Bug 1415358

Summary:	systemd-udevd and journald fail to start on i686 (systemd 232)
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	johannbg, john.ellson, lfelia, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-232-11.fc26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-30 14:35:07 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 Adam Williamson 2017-01-21 01:42:14 UTC

Since systemd 232 landed in Rawhide, udev and journald both fail to start during boot. This is obviously critical, boot never proceeds - it just loops forever, trying and failing to start both services for 90 seconds at a time. This affects (AFAICT) all i686 images, 100% of the time; every attempt to boot any of the Rawhide i686 images built since 20170107.n.1 (the compose where systemd 232 landed) fails.

If I run with all the suggested debugging tricks from https://freedesktop.org/wiki/Software/systemd/Debugging/ - systemd.log_level=debug systemd.log_target=console systemd.journald.forward_to_console=1 console=ttyS0,38400 - and observe the serial console, I see a bunch of these errors:

[    8.295846] systemd-udevd[533]: error getting socket: Protocol not supported

I'll attach the entire output after leaving it running for a few minutes. You can always find images for testing from the nightlies page here:

https://www.happyassassin.net/nightlies.html

just grab any of the 'Last built' i386 (i686) images and try to boot it. Live or installer image, doesn't matter.

Comment 1 Adam Williamson 2017-01-21 01:56:07 UTC

Looks like this is:

https://github.com/systemd/systemd/issues/4575

via Arch (thanks, Arch):

https://bugs.archlinux.org/task/51693

And this should fix it:

https://github.com/systemd/systemd/commit/469830d1426a91e0897c321fdc8ee428f0a750c1

I'll throw that at the Rawhide package and see how it goes.

Comment 2 Adam Williamson 2017-01-21 02:19:39 UTC

Unfortunately that patch doesn't backport cleanly to v232, and the adjustments necessary aren't trivial, there are cases where the patch touches code that was changed substantially in other ways between v232 and the patch's changes, so I'm not really comfortable with adapting the backport. I'll leave this to the systemd maintainers to decide what the best approach is, but please, it would be nice to have this fixed ASAP. Even though i686 is not a 'primary arch' any more, breaking it entirely is not great.

Comment 3 Zbigniew Jędrzejewski-Szmek 2017-01-30 14:35:07 UTC

The patches are in rawhide with systemd-232-11.fc26, please test.

Comment 4 Zbigniew Jędrzejewski-Szmek 2017-01-30 15:45:47 UTC

*** Bug 1416198 has been marked as a duplicate of this bug. ***

Comment 5 Veteran 2017-01-31 21:58:41 UTC

Yes this boots as expected. Thank you.