Description of problem: Boot hangs, usually at the following point [ ***] A start job is running for Network Manager Version-Release number of selected component (if applicable): I am not sure which component is causing this. systemd.x86_64 204-15.fc19 NetworkManager.x86_64 1:0.9.8.2-9.git20130709.fc19 kdm.x86_64 4.11.1-3.fc19 kernel.x86_64 3.11.2-201.fc19 How reproducible: Fails in: 1 out of 2 boots, 2 out of 3, last time about 10 times in a row. Steps to Reproduce: Power ON or reboot (shutdown -r now). Actual results: Boot hangs. Expected results: Boots to Graphics/KDE. Additional info: The system was upgraded from f17 -> f18 -> f19. I do not have the rhgb kernel command-line parameter - no plymouth. I do not know much the new systemd, journal tools. I looked up some commands in similar bugs and created a small script collecting logs. I collected several sets of logs. I am going to attach logs from one of them. I collected them by logging to TTY2 (Alt-F2). ---------------------- #!/bin/bash dt=$(date "+%Y-%m-%d_%H:%M") dir="/root/dbg_sysd.$dt" mkdir $dir cd $dir systemd-analyze > systemd-analyze.log 2>&1 systemd-analyze blame > systemd-analyze_blame.log 2>&1 systemd-analyze --fuzz=10ms critical-chain > systemd-analyze_--fuzz_10ms_critical-chain.log 2>&1 journalctl -b > journalctl_-b.log 2>&1 journalctl -o short-monotonic -ab > journalctl_-o_short_monotonic_-ab.log 2>&1 journalctl -o short-monotonic -ab -o verbose > journalctl_-o_short-monotonic_-ab_-o_verbose.log 2>&1 ---------------------- I also stored the legacy (messages, dmesg, etc.) logs. Let me know if / what else may help.
Created attachment 807243 [details] systemd-analyze > systemd-analyze.log
Created attachment 807245 [details] systemd-analyze blame > systemd-analyze_blame.log
Created attachment 807247 [details] systemd-analyze --fuzz=10ms critical-chain b> systemd-analyze_--fuzz_10ms_critical-chain.log
Created attachment 807250 [details] boot.log
Created attachment 807252 [details] journalctl -b > journalctl_-b.log
Created attachment 807253 [details] journalctl -o short-monotonic -ab > journalctl_-o_short_monotonic_-ab.log
Created attachment 807254 [details] journalctl -o short-monotonic -ab -o verbose > journalctl_-o_short-monotonic_-ab_-o_verbose.log
I have just found the following messages in the logs (journalctl_-b.log and journalctl_-o_short_monotonic_-ab.log): kdm[592]: X server startup timeout, terminating I am going to attach the Xorg.0.log and kdm.log and re-assign it rather to Xorg component. Could you please have a look at them? The boot now fail like 8-9 times out of 10? Thanks.
Created attachment 807892 [details] Xorg.0.log
Created attachment 807893 [details] kdm.log
I cannot reproduce the issue after a kernel update to 3.11.3-201.fc19.x86_64. I will report back if it happens again otherwise the bug can be closed.
Closing then.