Bug 692375 - system hangs start up
Summary: system hangs start up
Keywords:
Status: CLOSED DUPLICATE of bug 692137
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 07:25 UTC by Fabien Archambault
Modified: 2011-03-31 08:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 08:48:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabien Archambault 2011-03-31 07:25:24 UTC
Description of problem: The latest version of systemd (according to my tests) hangs on start up. This blocks the loading of the computer.


How reproducible: always (init 3 or 5)


Steps to Reproduce:
1. Start computer
2.
3.
  
Actual results: hangs the startup


Expected results: no hanging


Additional info:
I wanted to downgrade the version because first I thought it was abrt as it hanged there. Then after stopping it to load it hanged on D-Bus.
I checked all updates made today. I had the kernel so I tried the previous working version and it hangs. The only system thing is systemd.
Also when I boot in init 1 and do:
systemctl start network.service
With only the eth0 plugged (no wireless activated) the network never loads! I waited about 5 minutes (the cable is 1.5m in 100MB/s directly to the router).

Comment 1 Michal Schmidt 2011-03-31 08:30:00 UTC
There is a known problem with the SELinux policy not being ready for systemd-21. Please check if your problem is caused by SELinux by booting in permissive mode ("enforcing=0").

Comment 2 Fabien Archambault 2011-03-31 08:37:10 UTC
Hi,

this allows the system to boot. Everything seems ok without SELinux.

Comment 3 Michal Schmidt 2011-03-31 08:48:54 UTC

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


Note You need to log in before you can comment on or make changes to this bug.