| Summary: | shutdown hangs due to a user processes | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Larry Johnson <keepitsimpleengineer> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | keepitsimpleengineer |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | workaround PAM file for vclock. | ||
|
Description
Larry Johnson
2013-10-05 22:30:14 UTC
Can you start at the beginning and explain what commands did you issue, in what situation, and what happened? (How do you start vlock, etc. Also what is 08-1? If debug-shell is not working, please file a separate bug report.) 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: https://bbs.archlinux.org/viewtopic.php?pid=1333144#p1333144 So, let's first find out what this vclock thing is. Google search returns nothing interesting. Can you try:
find / -xdev -type f -exec grep -H vclock {} \;
It is vlock It is not vclock. vlock is invoked in .bash_profile when automatically starting xfce4. Apparently my xfce4 which was installed prior to systemd needs some work, which may resolve this problem. vlock issues notwithstanding, this shouldn't happen. I'm assuming that because of (buggy vlock configuration), your user's processes don't terminate when requested nicely, blocking shutdown. We should be able to reproduce it with a dummy loop. Apparently having vlock in the auto-start for xfce4 caused the problem (additional and subsequent problems due to my confusion). With vlock out of the start-up process for xfce4 the problem has disappeared. I recall it was added to alleviate some other problem which has faded from memory. Sorry for the confusion and thanks for the help. This should be fixed with 209. Closing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.