|
Description
Tomas Toth
2013-10-03 19:59:54 UTC
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. |