Hello all We have a problem with machines running systemd-37-15.fc16.x86_64 hanging on reboot.
We have a system that boots from an initramfs based on F16. Nothing much more special than yum --installroot and making a cpio archive out of it. We use the following kernel options that might be pertinent: plymouth.enable=0 readonlyroot systemd.log_level=debug systemd.log_target=kmsg Before trying to reboot, we stop all non-essential services, and unmount all file systems (just in case something there was causing problems). All that's left over when we hit shutdown -r is our read-only initramfs and a few main Fedora services. We were able to capture the systemd debugging logging towards the end of the shutdown process using netconsole: systemd[1]: Job mdmonitor-takeover.service/stop finished, result=done type=1130 audit(1333039788.810:1424): pid=0 uid=0 auid=4294967295 ses=4294967295 msg=': comm="mdmonitor-takeover" exe="/bin/systemd" hostname=? addr=? terminal=? res=success' type=1131 audit(1333039788.827:1425): pid=0 uid=0 auid=4294967295 ses=4294967295 msg=': comm="mdmonitor-takeover" exe="/bin/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: systemd-sysctl.service changed exited -> dead systemd[1]: Job systemd-sysctl.service/stop finished, result=done systemd[1]: systemd-modules-load.service changed exited -> dead systemd[1]: Job systemd-modules-load.service/stop finished, result=done type=1130 audit(1333039788.908:1428): pid=0 uid=0 auid=4294967295 ses=4294967295 msg=': comm="systemd-modules-load" exe="/bin/systemd" hostname=? addr=? terminal=? res=success' type=1131 audit(1333039788.925:1429): pid=0 uid=0 auid=4294967295 ses=4294967295 msg=': comm="systemd-modules-load" exe="/bin/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: swap.target changed active -> dead systemd[1]: Job swap.target/stop finished, result=done systemd[1]: systemd-vconsole-setup.service changed exited -> dead systemd[1]: Job systemd-vconsole-setup.service/stop finished, result=done systemd[1]: systemd-ask-password-wall.path changed waiting -> dead systemd[1]: Job systemd-ask-password-wall.path/stop finished, result=done systemd[1]: Received SIGCHLD from PID 8066 (ck-log-system-s). systemd[1]: Got SIGCHLD for process 8066 (ck-log-system-s) systemd[1]: Child 8066 died (code=exited, status=0/SUCCESS) systemd[1]: Child 8066 belongs to console-kit-log-system-stop.service systemd[1]: console-kit-log-system-stop.service: main process exited, code=exited, status=0 systemd[1]: console-kit-log-system-stop.service changed start -> dead systemd[1]: Job console-kit-log-system-stop.service/start finished, result=done systemd[1]: Accepted connection on private bus. systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: console-kit-log-system-stop.service: cgroup is empty systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: network.service: cgroup is empty systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local What is supposed to happen next in the shutdown process? Is there any way we can get more debugging info to find out why it is hanging? Thanks! Regards Albert _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel