Bug 723355 - System fails to boot with systemd-26-8
Summary: System fails to boot with systemd-26-8
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: i686
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 21:45 UTC by Jonathan Dieter
Modified: 2012-01-25 18:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-25 16:20:22 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.