[SOLVED] New desktop PC appears to hang on attempt to sleep

daigennki · 2022-11-27 10:57:36

Hi! Recently I moved my Arch install from my old PC (i7-6700K + ASUS Z170-K) to my new one (Ryzen 7900X + ASRock B650M PG Riptide WiFi) by means of bringing the NVMe drive over, and now the system seems to have trouble going to sleep. In the KDE menu, I click on "sleep", then the monitor turns off (goes into power saving mode), but the power light on the PC is still lit, its fans are still spinning, and the keyboard and mouse seem to be completely unresponsive, making a hard reset/forced shutdown the only option left. Num Lock and Caps Lock on the keyboard seem to be unresponsive too (no lights on the keyboard turn on or off). I've also made sure to remove the Intel microcode and install the AMD microcode. What gives?

journalctl when I try to get it to sleep:

11月 27 19:35:26 GUNGNIR-160126L systemd-logind[711]: The system will suspend now!
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.5736] manager: sleep: sleep requested (sleeping: no  enabled: yes)
11月 27 19:35:26 GUNGNIR-160126L dbus-daemon[709]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=734 comm="/usr/bin/NetworkManager --no-daemon")
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.5737] device (wlp8s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.5738] device (wlp8s0): set-hw-addr: reset MAC address to A8:93:4A:C1:55:81 (unmanage)
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.5740] manager: NetworkManager state is now ASLEEP
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.5741] device (enp9s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
11月 27 19:35:26 GUNGNIR-160126L kded5[948]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Starting Network Manager Script Dispatcher Service...
11月 27 19:35:26 GUNGNIR-160126L dbus-daemon[709]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Started Network Manager Script Dispatcher Service.
11月 27 19:35:26 GUNGNIR-160126L 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'
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6114] device (enp9s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
11月 27 19:35:26 GUNGNIR-160126L kernel: audit: type=1130 audit(1669545326.605:193): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 27 19:35:26 GUNGNIR-160126L kscreenlocker_greet[12480]: Qt: Session management error: networkIdsList argument is NULL
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6553] dhcp4 (enp9s0): canceled DHCP transaction
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6553] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6553] dhcp4 (enp9s0): state changed no lease
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6554] dhcp6 (enp9s0): canceled DHCP transaction
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6554] dhcp6 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.6554] dhcp6 (enp9s0): state changed no lease
11月 27 19:35:26 GUNGNIR-160126L systemd-resolved[636]: enp9s0: Bus client reset search domain list.
11月 27 19:35:26 GUNGNIR-160126L systemd-resolved[636]: enp9s0: Bus client set default route setting: no
11月 27 19:35:26 GUNGNIR-160126L systemd-resolved[636]: enp9s0: Bus client reset DNS server list.
11月 27 19:35:26 GUNGNIR-160126L kernel: r8169 0000:09:00.0 enp9s0: Link is Up - 1Gbps/Full - flow control rx/tx
11月 27 19:35:26 GUNGNIR-160126L kscreenlocker_greet[12480]: kf.kirigami: Failed to find a Kirigami platform plugin
11月 27 19:35:26 GUNGNIR-160126L kscreenlocker_greet[12480]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
11月 27 19:35:26 GUNGNIR-160126L NetworkManager[734]: <info>  [1669545326.7460] device (enp9s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 27 19:35:26 GUNGNIR-160126L kernel: r8169 0000:09:00.0 enp9s0: Link is Down
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Stopping Network Time Synchronization...
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: systemd-timesyncd.service: Deactivated successfully.
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Stopped Network Time Synchronization.
11月 27 19:35:26 GUNGNIR-160126L audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Reached target Sleep.
11月 27 19:35:26 GUNGNIR-160126L kernel: audit: type=1131 audit(1669545326.748:194): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 27 19:35:26 GUNGNIR-160126L audit: BPF prog-id=0 op=UNLOAD
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Starting System Suspend...
11月 27 19:35:26 GUNGNIR-160126L audit: BPF prog-id=34 op=LOAD
11月 27 19:35:26 GUNGNIR-160126L systemd[1]: Starting Network Time Synchronization...
11月 27 19:35:26 GUNGNIR-160126L kernel: audit: type=1334 audit(1669545326.802:195): prog-id=0 op=UNLOAD
11月 27 19:35:26 GUNGNIR-160126L kernel: audit: type=1334 audit(1669545326.802:196): prog-id=34 op=LOAD
11月 27 19:35:26 GUNGNIR-160126L systemd-sleep[12516]: Entering sleep state 'suspend'...
11月 27 19:35:26 GUNGNIR-160126L kernel: PM: suspend entry (s2idle)

Oh, and the GPU, an RX 5700 XT, was brought over from the old PC too.

Last edited by daigennki (2022-11-29 03:31:32)

d.ALT · 2022-11-27 17:53:13

Do you have some "weird" options enabled in Firmware Settings (UEFI) that maybe prevent your PC going into proper suspension? Is Windows' Fast Start disabled?

Last edited by d.ALT (2022-11-27 17:53:34)

daigennki · 2022-11-28 01:22:29

d.ALT wrote:

Do you have some "weird" options enabled in Firmware Settings (UEFI) that maybe prevent your PC going into proper suspension?

Not as far as I can tell. "Suspend to RAM" is set to "Auto" (the only other option is "Disabled"), and "Deep Sleep" is set to "Disabled".

d.ALT wrote:

Is Windows' Fast Start disabled?

Windows is not installed on this machine and Arch Linux is the only OS installed on it.

Last edited by daigennki (2022-11-28 01:22:53)

cfr · 2022-11-28 02:02:03

What happens if you enable "Deep Sleep"? Read the description first but s3 is called 'deep' on (some?) laptops. Perhaps that's why it is trying to suspend to s2idle rather than s3 (suspend to RAM)?

daigennki · 2022-11-28 03:07:12

Options for "Deep Sleep" are "Disabled", "Enabled in S5", and "Enabled in S4 & S5", so I would think it's irrelevant here, but I tried "Enabled in S4 & S5" anyways, and unsurprisingly that changed nothing.
I did try a BIOS update though, since there's a beta update on ASRock's website that says "Enhance S3 mode". It doesn't hang on sleep anymore, but now I have a different issue where it immediately wakes from sleep. Here's the journalctl now: https://gist.github.com/daigennki/8ecfe … a475f2874f
I did try both enabling and disabling deep sleep in S4 and S5, as well as disabling wake on PCIe (wake on LAN), and none of those helped.

cfr · 2022-11-28 03:27:48

A quick google with

amdgpu 0000:03:00.0: Refused to change power state from D0 to D3hot

turns up a different problem with sleep (but that maybe more like https://bbs.archlinux.org/viewtopic.php?id=273255, which is fixed?) and a hang when sleeping, but a different chip.

daigennki · 2022-11-28 12:24:34

Interesting, I upgraded the Linux kernel to the recently released 6.0.10.arch2-1, and that seems to have fixed the issue with it waking up immediately. When I do wake it up though, the screen resolution gets reset to 1080p@60Hz, and I can't change it back to the native resolution (4K@144Hz) in the KDE display settings (resolutions higher than 1080p aren't listed) until I reconnect the DisplayPort cable. What's up with that?
I will admit though that this monitor I'm using, an ASUS VG28UQL1A, is slow to wake from sleep, so maybe that's causing issues...

EDIT: I should note that I used the same monitor with the same graphics card in my previous PC, and I didn't have any of these issues there at all. I also disabled the Ryzen 7900X integrated GPU in BIOS, and that didn't help.

Last edited by daigennki (2022-11-28 12:42:42)

cfr · 2022-11-28 23:20:53

Check or post the journal and Xorg log (if you're using X). You can likely work around the problem with a sleep hook if you need to.

daigennki · 2022-11-29 03:31:06

Never mind, it looks like either the GPU or the monitor (or both, or maybe even something else in the system) don't like it when I wake it shortly after putting it into suspend. I left it in sleep mode for a while then woke it up, and none of the issues are present anymore, including the screen resolution issue. I rarely wake it shortly after putting it into suspend, making it basically a non-issue for me, so I'm marking this as solved.

Last edited by daigennki (2022-11-29 03:33:36)

Arch Linux

#1 2022-11-27 10:57:36

[SOLVED] New desktop PC appears to hang on attempt to sleep

#2 2022-11-27 17:53:13

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#3 2022-11-28 01:22:29

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#4 2022-11-28 02:02:03

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#5 2022-11-28 03:07:12

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#6 2022-11-28 03:27:48

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#7 2022-11-28 12:24:34

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#8 2022-11-28 23:20:53

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

#9 2022-11-29 03:31:06

Re: [SOLVED] New desktop PC appears to hang on attempt to sleep

Board footer