Bug 744465 - Boot took too much time on Fedora 16 Beta Live
Summary: Boot took too much time on Fedora 16 Beta Live
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-08 20:05 UTC by Yann Droneaud
Modified: 2011-12-05 23:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-05 23:06:55 UTC
Type: ---


Attachments (Terms of Use)
dmesg (123.32 KB, text/plain)
2011-10-08 20:05 UTC, Yann Droneaud
no flags Details

Description Yann Droneaud 2011-10-08 20:05:30 UTC
Created attachment 527045 [details]
dmesg

On a Samsung n210, booting Fedora 16 Beta Live LXDE on a USB stick,
boot took more than 5 minutes.

[   19.537536] systemd[1]: Reloading.
[   25.430264] systemd[1]: Reloading.
[   31.004252] systemd[1]: rc-local.service: control process exited, code=exited status=203
[   31.006759] systemd[1]: Unit rc-local.service entered failed state.
[  120.589167] systemd[1]: rsyslog.service operation timed out. Terminating.
[  120.589777] systemd[1]: NetworkManager.service operation timed out. Terminating.
[  120.590928] systemd[1]: sshd-keygen.service operation timed out. Terminating.
[  170.761386] systemd-logind[842]: Failed to start unit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[  215.589165] systemd[1]: rsyslog.service stopping timed out (2). Killing.
[  215.589731] systemd[1]: NetworkManager.service stopping timed out (2). Killing.
[  215.590726] systemd[1]: sshd-keygen.service stopping timed out (2). Killing.
[  215.591460] systemd[1]: Unit sshd-keygen.service entered failed state.
[  220.606169] systemd[1]: Unit NetworkManager.service entered failed state.
[  310.589181] systemd[1]: rsyslog.service still around after SIGKILL (2). Entering failed mode.
[  310.589387] systemd[1]: Unit rsyslog.service entered failed state.
[  311.426764] systemd[1]: Startup finished in 1s 541ms 95us (kernel) + 5s 818ms 16us (initrd) + 5min 4s 67ms 180us (userspace) = 5min 11s 426ms 291us.

Comment 1 Michal Schmidt 2011-10-10 23:40:56 UTC
It works for me. Is it reproducible? If yes, please boot with these parameters:
  log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg
and attach the new output of 'dmesg'.

Comment 2 Fedora Admin XMLRPC Client 2011-10-20 16:31:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.


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