Bug 89376

Summary:	systemd stops all services but does not poweroff most of the time (race-condition?)
Product:	systemd	Reporter:	fzacarias3k
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Shutdown sequence saved to /shutdown-log.txt by debug.sh

Description fzacarias3k 2015-03-01 16:03:12 UTC

Created attachment 113898 [details]
Shutdown sequence saved to /shutdown-log.txt by debug.sh

I'm running Debian Jessie. After the migration from sysvinit to systemd (version 215), my laptop does not poweroff anymore. All services stop and screen goes black but it won't turn off the power, no matter how long I wait. *Seldomly* it does work, which makes me guess a race-condition. Reverting to sysvinit fixes the issue, so there is a problem with systemd.

I followed the steps described here [1] to try to debug the problem myself. As described there, the command `sync && poweroff -f` works perfectly fine, further pointing into systemd's as the source of the problem.

I enabled the specified boot params but I don't get much log messages in dmesg anyway. See the attachement for the output of my laptop's poweroff sequence. As you can see, looks like systemd is trying to unmount the encrypted volume before other file-systems.

Note that my laptop's file-system layout is just the standard full-disk encryption employed by most (if not all) linux distros: unencrypted /boot partition + another big partition encrypted via dmcrypt, which contains a few LVM volumes (/, /home and swap).

I opened a bug for this on Debian's bugzilla some weeks ago [2] but it has not been updated in a while.
Please help!

[1] http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770090

Comment 1 fzacarias3k 2015-05-31 08:35:57 UTC

I cannot reproduce the issue anymore after a package upgrade. Please, look at the Debian bug for more details. [1]

I wish systemd's debugging output was more verbose to understand what is going on during the power off sequence. The feeling of not being able to understand what is going on with your own host is very unconfortable.
 
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770090

Comment 2 Lennart Poettering 2015-06-18 18:24:50 UTC

OK, closing then.

If you turn on debug logging, then you'll get a lot of info dumped to the logs/screen about what's going on during shutdown. You can also enable "debug-shell.service" and you'll get a shell on tty9 that is available all the time during sutdown, to explore things, and make additional checks.

Please see:

https://wiki.freedesktop.org/www/Software/systemd/Debugging/

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.