<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - shutdown hangs due to vclock infinite loop during PAM authenication." href="https://bugs.freedesktop.org/show_bug.cgi?id=70178#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - shutdown hangs due to vclock infinite loop during PAM authenication." href="https://bugs.freedesktop.org/show_bug.cgi?id=70178">bug 70178</a> from <a class="email" href="mailto:keepitsimpleengineer@gmail.com" title="Larry Johnson <keepitsimpleengineer@gmail.com>"> Larry Johnson</a> <pre>Commands issued: systemctl shutdown or any command to shutdown or reboot. The process of shutdown (also when rebooting) immediately stops with one line obscured in the bottom half. A hardware reset is required to complete/end the shutdown. When booting after this manner of shutting down, the /boot partition is marked unclean and must be fsck'd. Vclock is apparently started as a part of shutdown. I initially confused it with "vlock". I have no idea what vclock is or where it's sourced. 08-1 should have been 208-1 and refers to systemd-208-1-x86_64 The debug shell failed to work in systemd-207-3-x86_64 and in systemd-207-5-x86_64. It does work in systemd-208-1-x86_64. Failure was the obscured line on F9 was identical to the line on F1. In 208-1, F9 was the debug prompt and worked as expected. To shutdown without hanging, the following commands were issued as root: umount /dev/sdf2; sync; poweroff -f My forum post regarding this is here: <a href="https://bbs.archlinux.org/viewtopic.php?pid=1333144#p1333144">https://bbs.archlinux.org/viewtopic.php?pid=1333144#p1333144</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>