[SOLVED] System does not shutdown (systemd crash)

OdinEidolon · 2014-03-11 14:20:57

Hi all.
After last systemd update (I think!) my computer does not shutdown anymore. It hangs after:

[ OK ] Reached target shutdown.

with blinking cursor.

Journalctl tells me:

└──>  journalctl -e -n 10 -b -1
mar 10 22:41:19 M735T systemd[1]: Starting Unmount All Filesystems.
mar 10 22:41:19 M735T systemd[1]: Reached target Unmount All Filesystems.
mar 10 22:41:19 M735T systemd[1]: Starting Final Step.
mar 10 22:41:19 M735T systemd[1]: Reached target Final Step.
mar 10 22:41:19 M735T systemd[1]: Starting Power-Off...
mar 10 22:41:19 M735T systemd[1]: Shutting down.
mar 10 22:41:19 M735T systemd[1]: Assertion 'pos + 1 < (sizeof(command_line)/sizeof((command_line)[0]))' failed at src/core/main.c:1943, function main(). Aborting.
mar 10 22:41:19 M735T systemd[1]: Caught <ABRT>, dumped core as pid 6089.
mar 10 22:41:19 M735T systemd[1]: Freezing execution.
mar 10 22:41:19 M735T systemd-coredump[6090]: Process 6089 (systemd) dumped core.

Any idea why this happens?

Last edited by OdinEidolon (2014-06-29 09:17:25)

unikum · 2014-03-12 13:18:46

Same here.

OdinEidolon · 2014-03-12 13:21:11

COmbined with the fact that the systemd hook does break hibernation, I cannot stop my computer now

brain0 · 2014-03-12 22:47:23

Which version is this?

OdinEidolon · 2014-03-13 08:17:49

Currently 210-3. Problem still persists.

brain0 · 2014-03-13 08:22:43

There's 211 in testing, please try that, then report a bug.

OdinEidolon · 2014-03-13 08:44:10

brain0 wrote:

There's 211 in testing, please try that, then report a bug.

Tested once. Seems to work (Thanks!). Journalctl only reports one error at the end of boot which I do not think is important:

mar 13 09:38:52 M735T systemd[1]: Stopped Remount Root and Kernel File Systems.
mar 13 09:38:52 M735T systemd[1]: Starting Shutdown.
mar 13 09:38:52 M735T systemd[1]: Reached target Shutdown.
mar 13 09:38:52 M735T systemd[1]: Unmounted Temporary Directory.
mar 13 09:38:52 M735T systemd[1]: Starting Unmount All Filesystems.
mar 13 09:38:52 M735T systemd[1]: Reached target Unmount All Filesystems.
mar 13 09:38:52 M735T systemd[1]: Starting Final Step.
mar 13 09:38:52 M735T systemd[1]: Reached target Final Step.
mar 13 09:38:52 M735T systemd[1]: Starting Reboot...
mar 13 09:38:52 M735T systemd[1]: Shutting down.
mar 13 09:38:52 M735T systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
mar 13 09:38:52 M735T systemd[1]: Set hardware watchdog to 10min.
mar 13 09:38:52 M735T kernel: watchdog watchdog0: watchdog did not stop!
mar 13 09:38:52 M735T systemd-shutdown[1]: Sending SIGTERM to remaining processes...
mar 13 09:38:52 M735T systemd-journal[124]: Journal stopped

(watchdog did not stop)

Thank you again. Now they only need to fix hibernation!
When also the other people affected by the problem confirm this solves it I'll mark as solved.

brain0 · 2014-03-13 13:00:22

OdinEidolon wrote:

mar 13 09:38:52 M735T systemd[1]: Set hardware watchdog to 10min.
mar 13 09:38:52 M735T kernel: watchdog watchdog0: watchdog did not stop!
mar 13 09:38:52 M735T systemd-shutdown[1]: Sending SIGTERM to remaining processes...
mar 13 09:38:52 M735T systemd-journal[124]: Journal stopped

systemd sets the watchdog to 10 minutes, then closes it without stopping the timer. Usually, closing the watchdog without stopping it is a mistake, hence the kernel warns about it. In this case, it is intended behaviour: If systemd-shutdown fails to start, the watchdog will time out after 10 minutes and reboot the system.

OdinEidolon · 2014-03-13 13:01:51

brain0 wrote:

OdinEidolon wrote:
mar 13 09:38:52 M735T systemd[1]: Set hardware watchdog to 10min.
mar 13 09:38:52 M735T kernel: watchdog watchdog0: watchdog did not stop!
mar 13 09:38:52 M735T systemd-shutdown[1]: Sending SIGTERM to remaining processes...
mar 13 09:38:52 M735T systemd-journal[124]: Journal stopped
systemd sets the watchdog to 10 minutes, then closes it without stopping the timer. Usually, closing the watchdog without stopping it is a mistake, hence the kernel warns about it. In this case, it is intended behaviour: If systemd-shutdown fails to start, the watchdog will time out after 10 minutes and reboot the system.

Thanks for the clarification.

Arch Linux

#1 2014-03-11 14:20:57

[SOLVED] System does not shutdown (systemd crash)

#2 2014-03-12 13:18:46

Re: [SOLVED] System does not shutdown (systemd crash)

#3 2014-03-12 13:21:11

Re: [SOLVED] System does not shutdown (systemd crash)

#4 2014-03-12 22:47:23

Re: [SOLVED] System does not shutdown (systemd crash)

#5 2014-03-13 08:17:49

Re: [SOLVED] System does not shutdown (systemd crash)

#6 2014-03-13 08:22:43

Re: [SOLVED] System does not shutdown (systemd crash)

#7 2014-03-13 08:44:10

Re: [SOLVED] System does not shutdown (systemd crash)

#8 2014-03-13 13:00:22

Re: [SOLVED] System does not shutdown (systemd crash)

#9 2014-03-13 13:01:51

Re: [SOLVED] System does not shutdown (systemd crash)

Board footer