FS#37288 - systemd hangs on reboot/shutdown, eventually completes after some minutes

Attached to Project: Arch Linux
Opened by CB (cle1109) - Friday, 11 October 2013, 06:14 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 November 2013, 13:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

When I reboot or shutdown, the system hangs for several minutes, but it eventually completes. This is not a kernel issue, since sync && reboot -f works just fine.

Unfortunately, there doesn't seem to be relevant information in the debug log file of systemd (see attached). The part where it hangs is right at the bottom, but there is a gap of about 2 minutes with no information about what causes it to hang:

[ 187.570659] systemd[1]: Shutting down.
[ 187.713500] systemd-journald[125]: Received SIGTERM
[ 301.515175] EXT4-fs (sda3): re-mounted. Opts: (null)
[ 301.531622] EXT4-fs (sda3): re-mounted. Opts: (null)
[ 301.531647] EXT4-fs (sda3): re-mounted. Opts: (null)
[ 301.676164] EXT4-fs (sda3): re-mounted. Opts: data=ordered

This only occurs with systemd versions greater than 204-3 (which is the last version that works for me).

Steps to reproduce:
1. Boot into a current up-to-date Arch Linux system.
2. Either reboot or shutdown the system.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 03 November 2013, 13:49 GMT
Reason for closing:  Upstream
Comment by patrick (potomac) - Friday, 11 October 2013, 20:37 GMT
same problems for me, random hangs under virtualbox, after one or two minutes systemd can resume the reboot/shutdown, no errors messages in logs files,

after further investigations I discover that it seems to be a timing problem/race competition between process when systemd tries to shutdown them,

because if I shutdown manually some processes under KDE before the reboot then systemd can do his job without problems, no hangs
Comment by patrick (potomac) - Saturday, 12 October 2013, 22:34 GMT
I notice if I type "systemctl" on a console under KDE then the bug is easily triggered
Comment by Karol Błażewicz (karol) - Sunday, 03 November 2013, 09:27 GMT
Is it a duplicate of  FS#37007  ?
Comment by Dave Reisner (falconindy) - Sunday, 03 November 2013, 13:48 GMT
No, it isn't. This happens because the dbus daemon goes away on shutdown.

Upstream isn't interested in addressing this directly, as kdbus is the solution.

Loading...