System freezes second after waking up from suspend

darklight · 2016-12-27 10:21:43

I recently did a full system upgrade (pacman -Syu) for the first time since Oct 22, and now I am experiencing a weird issue. It's somewhat alike other issues I've seen here, but it seems to have some subtle differences.

Basically when suspend my PC and then wake it up again, it will quickly 'freeze'. The freeze is a weird one, where if I have a terminal open I will still see the cursor blinking for a few seconds, but then I won't see the clock ticking (I'm using i3 with the default i3bar), I can't move my mouse, my keyboard seems to do nothing either, and my terminal will shortly after that freeze as well.
Though there is a weird case where sometimes the cursor in my terminal won't stop blinking, so there is still something going on, albeit very little.
My statusbar will sometimes show me as disconnected, but sometimes it will quickly reconnect before everything gets stuck. The only way I have found so far to get out of it is to just hold the power button and force a shutdown that way, so I can then restart my pc. Also my laptop will not suspend on closing after it got stuck.

I'm now on the latest versions, including 'x86_64 Linux 4.8.13-1-ARCH' as a kernel. I was previously using 4.8.4-1 where everything was fine. I have seen some issues like this related to the nvidia drivers, but I'm using an AMD/ATI GPU, with as far as I'm aware, the correct drivers.

Also my logs don't show anything interesting, journalctl gives me:

Dec 27 01:42:18 larch systemd-logind[400]: Lid closed.
Dec 27 01:42:18 larch systemd-logind[400]: Suspending...
Dec 27 01:42:18 larch systemd[1]: Reached target Sleep.
Dec 27 01:42:18 larch systemd[1]: Starting Suspend...
Dec 27 01:42:18 larch systemd-sleep[1089]: Suspending system...
-- Reboot --

To make sure, I have disabled the lock screen, but the issue remains (if I do have a lock screen the same things happen: it will record keystrokes for a moment (about a second) after which it gets stuck.
The issue can be easily reproduced by simply doing 'systemctl suspend'.

Also,

echo freeze > /sys/power/state

works, but

echo mem > /sys/power/state

does not; though I guess that's not that surprising.

I'm thinking of doing a rollback on my kernel but I'm not sure how safe that is, and I have no clue whether that will solve the problem.

EDIT: I have now done a rollback, using 4.8.4 which was still in my pacman cache, solving the issue.

Last edited by darklight (2016-12-27 22:23:09)

darklight · 2016-12-27 12:20:38

I have now tried to see what happens without anything graphical whatsoever, so I just logged in as root, did 'systemctl suspend' and it crashed after a lot of error messages. These are probably interesting but I don't really know where to find them.

Slithery · 2016-12-27 12:25:05

https://wiki.archlinux.org/index.php/Systemd#Journal

darklight · 2016-12-27 12:39:18

I have now downgraded the kernel back to 4.8.4, and the problem seems to be gone. At this point I'd be very happy to know the following things:

What do I do now? Obviously I don't want the kernel to be upgraded to 4.8.13 on my next upgrade or something like that, but I'd like to get upgrades on later versions where the issue might be fixed.
Where can I read the content of the logs so I can make a proper bug report
Should I report this to the Linux bugtracker or the Arch bugtracker?

darklight · 2016-12-27 12:45:26

Thanks for the suggestion slithery but as I said, for some reason there is nothing interesting in there. The logs end before the crash occurs.
Maybe it's just console output and not anything that got logged?

seth · 2016-12-27 14:50:56

The crash will prevent the fsync, so nothing ends on disk.
If "a lot" is not "too much" -> camera (but only post a link or thumbnail here)
If it is "too much" the only answer i'd know is to reduce this useless <rant> of <rant> journald to simply forward stuff to a real log system (like rsyslog) and wire the messages to another terminal/machine.
At least i'm not aware of such capabilities which would have made it into journald :-(

techhat · 2016-12-27 22:16:11

I'm in the same boat, though I had the issue appear for me after updating about 2 weeks ago, after no updates for maybe 2 or 3 weeks. I would really love to know what's causing this and how to fix it.

techhat · 2016-12-27 22:33:42

Update: Setting /sys/power/disk to suspend seems to to fix the problem on my system.

# cat /sys/power/disk 
[platform] shutdown reboot suspend test_resume 
# echo suspend > /sys/power/disk
# cat /sys/power/disk
platform shutdown reboot [suspend] test_resume

Last edited by techhat (2016-12-27 22:47:34)

darklight · 2016-12-28 00:02:46

Nice, isn't that just storing the info kept while suspended on disk instead of in memory?

techhat · 2016-12-28 03:35:36

No idea. But when I close the lid, my laptop behaves the way it did before, so far as I can tell, and that's all I need to be happy.

lemondreas · 2021-08-15 09:18:25

@techman

thanks for the help, i had this issue the whole night. i <3 the arch way

Arch Linux

#1 2016-12-27 10:21:43

System freezes second after waking up from suspend

#2 2016-12-27 12:20:38

Re: System freezes second after waking up from suspend

#3 2016-12-27 12:25:05

Re: System freezes second after waking up from suspend

#4 2016-12-27 12:39:18

Re: System freezes second after waking up from suspend

#5 2016-12-27 12:45:26

Re: System freezes second after waking up from suspend

#6 2016-12-27 14:50:56

Re: System freezes second after waking up from suspend

#7 2016-12-27 22:16:11

Re: System freezes second after waking up from suspend

#8 2016-12-27 22:33:42

Re: System freezes second after waking up from suspend

#9 2016-12-28 00:02:46

Re: System freezes second after waking up from suspend

#10 2016-12-28 03:35:36

Re: System freezes second after waking up from suspend

#11 2021-08-15 09:18:25

Re: System freezes second after waking up from suspend

Board footer