Bug 723355

Summary:	System fails to boot with systemd-26-8
Product:	[Fedora] Fedora	Reporter:	Jonathan Dieter <jdieter>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	15	CC:	harald, johannbg, johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-25 16:20:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jonathan Dieter 2011-07-19 21:45:43 UTC

Description of problem:
When I turned my laptop on this evening, it refused to boot.  The plymouth graphic never completed, and pressing escape to show the boot messages didn't show anything that jumped out.  This is the first time I've booted my laptop since upgrading from systemd-26-5 to 26-8.  Running yum downgrade systemd systemd-units systemd-sysv fixed the problem (and I'm now running 26-1).

Version-Release number of selected component (if applicable):
systemd-26-8.fc15.i686

How reproducible:
Always

Steps to Reproduce:
1. Turn computer on
2.
3.
  
Actual results:
It freezes

Expected results:
Normal boot

Additional info:

Comment 1 Michal Schmidt 2011-07-20 11:05:25 UTC

Please remove "rhgb quiet" from the kernel command line, add "systemd.log_level=debug" and see what's on the screen when it freezes. Thanks.
Try waiting for 5 minutes to see if a timeout kicks in.

Comment 2 Fedora Admin XMLRPC Client 2011-10-20 16:28:39 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Jonathan Dieter 2012-01-25 18:00:00 UTC

Sorry, I just realized that I had forgotten about this bug.  Systemd is booting fine now in F16.  IIRC, it was having problems booting the akmods.service from RPM Fusion and I just shut it off.  Again, my apologies for not closing it myself.