Bug 4186 - 2_a3: Checking for new hardware taking minutes to run in runlevel3
Summary: 2_a3: Checking for new hardware taking minutes to run in runlevel3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120
  Show dependency tree / graph
 
Reported: 2012-01-18 18:19 CET by Bit Twister
Modified: 2012-01-20 05:00 CET (History)
2 users (show)

See Also:
Source RPM: systemd-38-6.mga2.src.rpm
CVE:
Status comment:

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

Description Bit Twister 2012-01-18 18:19:15 CET 
Description of problem:

Installed latest systemd updates, rebooted. Looking normal then hangs for several minutes at Checking for new hardware


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


How reproducible: Always


Steps to Reproduce:
1. In stall updates
2. set system to boot runlevel 3
3. remove splash=whatever
4. reboot

Have seen 3 system-unit releases and bug 4133 still exists.  :(
Comment 1 Bit Twister 2012-01-18 19:52:32 CET 
Jan 18 12:45:29 wb2 systemd[1]: Startup finished in 633ms 278us (kernel) + 5s 77ms 273us (initrd) + 8min 18s 967ms 439us (userspace) = 8min 24s 677ms 990us.

I was spoiled with the 42 second times I used to get.
Manuel Hiebel 2012-01-18 22:34:40 CET

Blocks: (none) => 2120

etienne FR 2012-01-19 10:23:37 CET

CC: (none) => etiennedau-site

Comment 2 Curtis Hildebrand 2012-01-20 02:11:30 CET 
Same here although I boot to runlevel 5 (is that now called graphical.target?).  I'm getting a 6min userspace time since installing systemd-38-6.

Also, my system freezes on a shutdown at "Checking new hardware".  I have to use Alt-SysReq to shutdown.

Currently at systemd-38-7.mga2

CC: (none) => curtis.h.news

Comment 3 Bit Twister 2012-01-20 05:00:26 CET 
systemd-38-8 resolved the problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.