Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
Opened by CB (cle1109) - Friday, 11 October 2013, 06:14 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 November 2013, 13:49 GMT
|
DetailsWhen 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
Sunday, 03 November 2013, 13:49 GMT
Reason for closing: Upstream
shutdown-log.txt
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
FS#37007?Upstream isn't interested in addressing this directly, as kdbus is the solution.