Hi, > On Monday, 15 December 2014 10:54 PM, P J P wrote: > and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0. I > have hit ># shutdown -r now >and boot-up has stalled at the same spot again. Let's see...
On a VM I had enabled 'CONFIG_LOCKUP_DETECTOR=y' & 'CONFIG_DETECT_HUNG_TASK=y' to detect hung tasks and to panic on hard or soft kernel lock-ups. After a while it did panic with a hung task trace. > -> http://fpaste.org/159929/ > -> http://fpaste.org/159938/ > > Even after setting these two configuration options, system boot halts at the > same spot as earlier. The fpaste link above is after setting above two > configuration options. On another machine that I left over night, it says - Failed to load SELinux policy. Freezing. === ... Starting Switch Root... [ 4.615752] systemd[1]: Switching root. [ 4.632717] systemd-journald[126]: Received SIGTERM from PID 1 (systemd). [ 5.296874] audit: type=1404 audit(1418662423.615:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 [ 302.048179] kworker/dying (32) used greatest stack depth: 12976 bytes left [13112.020686] systemd[1]: Failed to load SELinux policy. Freezing. === I've restarted it with - systemd.log_level=debug systemd.log_target=kmsg enforcing=0. Is there a way to see what systemd(1) is doing after it says - Starting Switch Root... - ? --- Regards -P J P http://feedmug.com _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel