Unable to wake from sleep/hibernation (?) on desktop

parski · 2021-10-24 07:18:56

The Problem
When I leave my computer for a while (over night most recently) and come back to it the power indicator LED is lit (as opposed to flashing/pulsating which it usually is when the PC is sleeping) it will not wake after first gently moving the mouse, then pressing escape, then pressing a bunch of keys, then short pressing the power switch. On my monitor I get "no signal".

Logs
Here is the journal entry (is that what we call the system log now?) from this morning. 08:21 is when I started to shake the mouse I would guess but I'm not 100% sure.

okt 24 05:49:07 desk avahi-daemon[473]: Withdrawing address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.
okt 24 05:52:07 desk avahi-daemon[473]: Registering new address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.*.
okt 24 05:52:08 desk avahi-daemon[473]: Withdrawing address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.
okt 24 05:55:08 desk avahi-daemon[473]: Registering new address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.*.
okt 24 05:55:09 desk avahi-daemon[473]: Withdrawing address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.
okt 24 05:58:08 desk avahi-daemon[473]: Registering new address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.*.
okt 24 05:58:09 desk avahi-daemon[473]: Withdrawing address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.
okt 24 06:01:09 desk avahi-daemon[473]: Registering new address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.*.
okt 24 06:01:10 desk avahi-daemon[473]: Withdrawing address record for fd3c:8de4:1351:3:95f3:9798:4cf:10ff on enp0s31f6.
okt 24 06:05:05 desk plasmashell[1079]: libkcups: Renew-Subscription last error: 0 successful-ok
okt 24 06:06:32 desk avahi-daemon[473]: Leaving mDNS multicast group on interface enp0s31f6.IPv6 with address fd3c:8de4:1351:3:95f3:9798:4cf:10ff.
okt 24 06:06:32 desk avahi-daemon[473]: Joining mDNS multicast group on interface enp0s31f6.IPv6 with address fd78:1e0d:5dc0:3:40d3:a2ab:e57d:a692.
okt 24 07:03:25 desk plasmashell[1079]: libkcups: Renew-Subscription last error: 0 successful-ok
okt 24 08:01:45 desk plasmashell[1079]: libkcups: Renew-Subscription last error: 0 successful-ok
okt 24 08:21:47 desk NetworkManager[475]: <info>  [1635056507.2704] dhcp4 (enp0s31f6): state changed bound -> extended, address=10.110.110.10
okt 24 08:21:47 desk dbus-daemon[474]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=475 comm="/usr/bin/NetworkManager --no-daemon ")
okt 24 08:21:47 desk systemd[1]: Starting Network Manager Script Dispatcher Service...
okt 24 08:21:47 desk dbus-daemon[474]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
okt 24 08:21:47 desk systemd[1]: Started Network Manager Script Dispatcher Service.
okt 24 08:21:47 desk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
okt 24 08:21:47 desk kernel: audit: type=1130 audit(1635056507.282:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
okt 24 08:21:57 desk systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
okt 24 08:21:57 desk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
okt 24 08:21:57 desk kernel: audit: type=1131 audit(1635056517.169:126): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Complete log here.

Specifications
I'm using a desktop PC with a Intel i7 8700K (Coffee Lake) and an Nvidia RTX 3080. It's not exactly Arch, I'm on EndeavourOS, but I'm on kernel 5.14.14-arch1-1 and it's a pretty fresh install with KDE Plasma and the non-free proprietary Nvidia driver.

Help would be very much appreciated, I would love to be able to sleep/hibernate to save energy.

[Edit]

I should add that I'm able to both sleep and hibernate manually by pressing the Sleep and Hibernate buttons respectively in the launcher, it's just the automated one that's messed up. Or maybe it's a screen saver that crashes the kernel, I don't know.

Last edited by parski (2021-10-24 07:27:12)

seth · 2021-10-24 08:09:31

There's no trace of an S3/S4 in the linked journal (which also seems to be for a reboot that starts at 08:46:01)
=> "sudo journalctl -b -1"?

parski · 2021-10-24 14:28:18

seth wrote:

There's no trace of an S3/S4 in the linked journal (which also seems to be for a reboot that starts at 08:46:01)
=> "sudo journalctl -b -1"?

Hmm, maybe it's not an S3 or S4 that happens at all. I tried leaving the machine on and going for a walk today. When I came home the power LED was solid on and the display said "no input signal". I couldn't "wake" the machine so I force powered it off by holding the power button and then powered it on again.

Here is the output of the command you wrote: Pastebin.

The weird thing is that I can sleep and hibernate fine if I do it manually but walking away from the machine just kills the display output or something.

By the way, journalctl is really cool. I've never seen it before this OS install. Really slick!

seth · 2021-10-24 14:58:12

The log runs from 11:34:48 until 15:44:22, there's
11:59:50 desk kscreenlocker_greet
12:52:37 desk kscreenlocker_greet
14:10:10 desk kscreenlocker_greet
14:18:24 desk kscreenlocker_greet
14:40:24 desk kscreenlocker_greet

So unless you've set the system to sleep ~65 minutes after being locked, that's probably not what's going on.

1. can you reproduce this when leaving the system *without* it being locked (either by you or automatically)?
2. What is you eg. set it to suspend to RAM after a 20 minutes idle timeout?

parski · 2021-10-26 13:04:32

I don't know what has changed but now the computer won't go to sleep when idle, it just goes to the lock screen. I've read about bugs in KDE Plasma where it won't save settings properly and I think maybe a setting I set previously has kicked in where I disabled sleep when idleing. However, I still get the behavior when shutting down or restarting the PC. If I select Shut Down in the menu it closes all my open software and appears to be shutting down but it's stuck indefinetely after it's stopped outputting a signal to the display. Same problem if I press Restart. It appears to hang somewhere between closing the software and actual power off with the exact same symptoms as when I had the "sleep" and "hibernation" problems. I'll see if I can get some helpful log output.

[Edit]

Hmm, I'm getting some really weird issues at the end of this log.

Last edited by parski (2021-10-26 13:08:37)

seth · 2021-10-26 13:25:53

Plasma crashes on exit, there've been similar threads recently.
Edit: https://bbs.archlinux.org/viewtopic.php?id=269549

On the original issue, did you try to disable TLP?

Last edited by seth (2021-10-26 13:28:52)

parski · 2021-10-27 07:08:48

It happened again this morning. It appears it needs more idle time than what I manage to put in during a day. Here is the log: Link

I'm not sure when I left the machine but it was ballpark around 21-22. I tried waking it at 09:01.

I will look into what TLP is and how to disable it. Thanks!

seth · 2021-10-27 07:18:18

The system was still running at 08:49:35
1. when this happens can you simply switch to a different TTY? (ctrl+alt+f2,f3,f4,…)
2. Install and start/enable openssh, https://wiki.archlinux.org/title/OpenSSH - when this happens, try to ssh into the system.

I think the GUI is frozen and unable to break DPMS, maybe because the input devices are lost (are they maybe wired to a USB hub on the monitor?)

parski · 2021-10-27 10:20:53

seth wrote:

The system was still running at 08:49:35
1. when this happens can you simply switch to a different TTY? (ctrl+alt+f2,f3,f4,…)
2. Install and start/enable openssh, https://wiki.archlinux.org/title/OpenSSH - when this happens, try to ssh into the system.
I think the GUI is frozen and unable to break DPMS, maybe because the input devices are lost (are they maybe wired to a USB hub on the monitor?)

1) Will try.
2) Will do.

Mouse, keyboard, mic and audio output are all connected to a USB hub. Not on the monitor though, that's router separately. Or rather it's a USB switch, I have two systems connected to it. I'll double check that it hasn't forfeited the connection next time it happens.

Arch Linux

#1 2021-10-24 07:18:56

Unable to wake from sleep/hibernation (?) on desktop

#2 2021-10-24 08:09:31

Re: Unable to wake from sleep/hibernation (?) on desktop

#3 2021-10-24 14:28:18

Re: Unable to wake from sleep/hibernation (?) on desktop

#4 2021-10-24 14:58:12

Re: Unable to wake from sleep/hibernation (?) on desktop

#5 2021-10-26 13:04:32

Re: Unable to wake from sleep/hibernation (?) on desktop

#6 2021-10-26 13:25:53

Re: Unable to wake from sleep/hibernation (?) on desktop

#7 2021-10-27 07:08:48

Re: Unable to wake from sleep/hibernation (?) on desktop

#8 2021-10-27 07:18:18

Re: Unable to wake from sleep/hibernation (?) on desktop

#9 2021-10-27 10:20:53

Re: Unable to wake from sleep/hibernation (?) on desktop

Board footer