Cannot shutdown/reboot

forgetmenot · 2019-10-19 12:28:10

Hello, since some point in time I can no longer shut down or reboot my pc normally by issuing shutdown/poweroff/halt/reboot commands. When I try to do this, the system does terminate (seemingly), it stops responding to input from keyboard (can't even REISUB at this point), but the machine does not get powered down automatically, it looks as if it's still operating (so for example I can hear the fan on my cpu radiator still rotating) although the screen turns off and the monitor reports "No signal", and I have to switch off the psu to be able to restart my pc. Rebooting via REISUB works all right though, so I guess there's an issue with systemd. What can I try in order to diagnose the problem?

Last edited by forgetmenot (2019-10-19 12:51:44)

loqs · 2019-10-20 01:48:12

What does the journal contain for a shutdown? Have you tried downgrading packages to locate which update caused the issue?

forgetmenot · 2019-10-20 16:13:22

Thank you for your help.

Here's the entire journal log for the previous boot:
https://pastebin.com/2a8Da3UT

I guess the logs pertaining to the reboot start at line 1251. Can you see anything wrong/suspicious there?

Honestly I haven't the slightest idea how I would track after what update the problem emerged, since it's been 2 weeks maybe (really hadn't the time to get to this sooner) and I did not pay attention to the critical packages receiving any updates. I might try to downgrade systemd itself, is that possible?

Last edited by forgetmenot (2019-10-20 16:54:48)

bwidlar · 2019-10-20 16:33:31

I have the same problem, sometimes arch doesnt shutdown/reboot since one month ago.

I have installed the lts kernel, and it seems its working now while I wait for a fix.

Wild Penguin · 2019-10-21 07:13:39

I've had a similar problem related to a Kernel memory module leak (amdgpu?). The system will hang after Journal has stopped (in my case screen was black because the graphics driver had crashed). If I waited a long time, after 15 minutes (or so) the computer would finally actually reboot or poweroff (depending on what I've told it to do) - with nothing in journal to indicate what it was doing all this time (ending in "Journal stopped" ~15 minutes before actual shutdown)! Not saying you guys have the same problem, just stating that some Kernel problem could cause this - apparently it still tries to de-initialize something after stopping journal? Also, after the "hang", SysRq didn't work here, either (if I try SysRq before making a regular shutdown / reboot via systemd, it would and does work) - EDIT: actually, now that I dig into my memory more, I'm not sure about SysRq anymore. It might have worked after all (my memory is a bit hazy on this detail), and I haven't reproduced this lately.

I guess there is nothing to do to get information from this state (i.e. graphics driver stopped for one reason or another, and journal has stopped logging) - unless you connect a serial console into a computer, which might spit out some Kernel errors?

Last edited by Wild Penguin (2019-10-21 07:16:34)

bwidlar · 2019-10-21 09:18:10

Maybe?
https://github.com/systemd/systemd/issues/13804

Wild Penguin · 2019-10-21 11:41:07

bwidlar: That would be a good candidate, but in these cases Journald has stopped. That is the very last entry in a normal reboot, and all "hung" processes which systemd is waiting for, are reported before that - I know because I've experienced that, too - whatever has crashed, causes extensively long waits with systemd. But in that case, the delay can be seen in the log!

loqs · 2019-10-21 16:00:36

Using Arch_Linux_Archive#How_to_restore_all_packages_to_a_specific_date
can you locate the first day the issue occurs and provide the update list for that day from the previous?

Last edited by loqs (2019-10-21 16:00:58)

forgetmenot · 2019-11-09 12:16:50

Hey. I tried to reboot via sudo shutdown -r now today (after not doing so for a couple of weeks) and now it works without issues, that is my pc was able to reboot! So it seems the problem has been solved by itself lol. Probably this was fixed by one of the recent updates, but I still don't know what exactly was causing this problem, maybe checking release notes and bug tracker lists for the latest kernel and/or systemd versions will help to get some clues to this.

Last edited by forgetmenot (2019-11-09 12:26:12)

Arch Linux

#1 2019-10-19 12:28:10

Cannot shutdown/reboot

#2 2019-10-20 01:48:12

Re: Cannot shutdown/reboot

#3 2019-10-20 16:13:22

Re: Cannot shutdown/reboot

#4 2019-10-20 16:33:31

Re: Cannot shutdown/reboot

#5 2019-10-21 07:13:39

Re: Cannot shutdown/reboot

#6 2019-10-21 09:18:10

Re: Cannot shutdown/reboot

#7 2019-10-21 11:41:07

Re: Cannot shutdown/reboot

#8 2019-10-21 16:00:36

Re: Cannot shutdown/reboot

#9 2019-11-09 12:16:50

Re: Cannot shutdown/reboot

Board footer