| Summary: | Boot took too much time on Fedora 16 Beta Live | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yann Droneaud <yann> | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | dennis, harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-05 23:06:55 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
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'. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. |
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.