Suspend/Wake Issue related to GNOME

[portbound]

I'm trying to debug an intermittent issue I have where my system fails to resume from s2idle suspend

Specs:
Lenovo Yoga 7 (AMD)
Fedora 43
GNOME 49
Kernel 6.19

What happens:
If I suspend my session by closing the laptop, hitting the power button, running systemctl suspend, or selecting suspend from the power menu on the desktop, the session suspends as expected.

When I try to wake the system by opening the lid, pressing a button on the keyboard, or hitting the power button, there's about a 75% chance that it will fail to resume. They keyboard backlight turns on, the screen turns on but it's black, and it hangs for a few seconds before rebooting.

If I do something stateful like toggle Num Lock before trying to suspend, the keyboard backlight shows Num Lock is enabled while the system tries to wake up. But after a few seconds it turns off and the machine restarts. So I assume it's crashing at some step while it tries to thaw my session.

I've seen a ton of threads like this, so I know I'm not the only one:
https://discussion.fedoraproject.org/t/yoga-7-wont-wake-from-sleep/104393/20

But they all seem to focus on regressions between kernel versions, or limitations of the s2idle suspend state as compared to something more robust like s3. In my case at least, don't think this is the problem.

I've run a few different configurations on this machine.

• Pop!_OS with CosmicDE -> no issues
• EndeavourOS with Gnome -> same issues
• Arch with Hyprland -> no issues
• Fedora with CosmicDE -> no issues
• Fedora with Xfce -> no issues

I think it's got something to do with GNOME?

Other things I've tried:

• Disabled Flip to Wake in the Bios
• Tried disabling power-profiles-daemon
• Older kernels
• Upgrading to Fedora 44 with GNOME 50

Here's the journalctl output for a failed wakeup.

Apr 28 21:11:55 nox systemd-logind[1053]: The system will suspend now!
Apr 28 21:11:55 nox ModemManager[1133]: <msg> [sleep-monitor-systemd] system is about to suspend
Apr 28 21:11:55 nox ModemManager[1133]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.2303] manager: sleep: sleep requested (sleeping: no enabled: yes)
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.2310] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.2313] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.2315] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Apr 28 21:11:55 nox ghostty[5321]: info(stream): OSC 1 (change icon) received and ignored icon=~
Apr 28 21:11:55 nox systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Apr 28 21:11:55 nox systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Apr 28 21:11:55 nox audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 28 21:11:55 nox kernel: wlp2s0: deauthenticating from 12:a7:93:fb:a1:ec by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 28 21:11:55 nox gnome-shell[3434]: Type GITypeInfo of property AccountsService.User:assword-mode does not match return type GITypeInfo of getter get_password_mode. Falling back to slow path
Apr 28 21:11:55 nox wpa_supplicant[1360]: nl80211: send_event_marker failed: Source based routing not supported
Apr 28 21:11:55 nox wpa_supplicant[1360]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=12:a7:93:fb:a1:ec reason=3 locally_generated=1
Apr 28 21:11:55 nox wpa_supplicant[1360]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4756] device (wlp2s0): supplicant interface state: completed -> disconnected
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4760] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Apr 28 21:11:55 nox avahi-daemon[1002]: Withdrawing address record for 2600:8805:3d06::20fe on wlp2s0.
Apr 28 21:11:55 nox avahi-daemon[1002]: Withdrawing address record for 2600:8805:3d06:0:66e2:2e2f:875b:a958 on wlp2s0.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4768] dhcp4 (wlp2s0): canceled DHCP transaction
Apr 28 21:11:55 nox avahi-daemon[1002]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2600:8805:3d06:0:66e2:2e2f:875b:a958.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4768] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 28 21:11:55 nox avahi-daemon[1002]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::aac0:34cf:e2f4:700.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4769] dhcp4 (wlp2s0): state changed no lease
Apr 28 21:11:55 nox avahi-daemon[1002]: Registering new address record for fe80::aac0:34cf:e2f4:700 on wlp2s0.*.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4771] dhcp6 (wlp2s0): canceled DHCP transaction
Apr 28 21:11:55 nox avahi-daemon[1002]: Withdrawing address record for fe80::aac0:34cf:e2f4:700 on wlp2s0.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4771] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 28 21:11:55 nox avahi-daemon[1002]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::aac0:34cf:e2f4:700.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.4771] dhcp6 (wlp2s0): state changed no lease
Apr 28 21:11:55 nox avahi-daemon[1002]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Apr 28 21:11:55 nox audit[1134]: NETFILTER_CFG table=firewalld:8 family=1 entries=26 op=nft_unregister_rule pid=1134 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Apr 28 21:11:55 nox avahi-daemon[1002]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 28 21:11:55 nox avahi-daemon[1002]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:11:55 nox avahi-daemon[1002]: Withdrawing address record for 192.168.0.83 on wlp2s0.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.5339] device (wlp2s0): set-hw-addr: set MAC address to 3E:9D:73:FA:1D:AC (scanning)
Apr 28 21:11:55 nox avahi-daemon[1002]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:11:55 nox avahi-daemon[1002]: New relevant interface wlp2s0.IPv4 for mDNS.
Apr 28 21:11:55 nox avahi-daemon[1002]: Registering new address record for 192.168.0.83 on wlp2s0.IPv4.
Apr 28 21:11:55 nox avahi-daemon[1002]: Withdrawing address record for 192.168.0.83 on wlp2s0.
Apr 28 21:11:55 nox avahi-daemon[1002]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:11:55 nox avahi-daemon[1002]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 28 21:11:55 nox systemd-resolved[968]: wlp2s0: Bus client set default route setting: no
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.6038] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.6039] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Apr 28 21:11:55 nox systemd-resolved[968]: wlp2s0: Bus client reset DNS server list.
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.6048] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 28 21:11:55 nox chronyd[1009]: Source 2602:f95b:2::1 offline
Apr 28 21:11:55 nox chronyd[1009]: Source 2607:7c80:54:3::56 offline
Apr 28 21:11:55 nox chronyd[1009]: Source 2a01:7e03::2000:93ff:fe22:34e4 offline
Apr 28 21:11:55 nox chronyd[1009]: Can't synchronise: no selectable sources (4 unreachable sources)
Apr 28 21:11:55 nox chronyd[1009]: Source 2606:4700:f1::1 offline
Apr 28 21:11:55 nox geoclue[1811]: WiFi scan failed
Apr 28 21:11:55 nox NetworkManager[1229]: <info> [1777425115.6530] device (wlp2s0): set-hw-addr: reset MAC address to 4C:23:38:48:FA:53 (unmanage)
Apr 28 21:11:55 nox wpa_supplicant[1360]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:11:55 nox wpa_supplicant[1360]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:11:55 nox wpa_supplicant[1360]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
Apr 28 21:11:55 nox wpa_supplicant[1360]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:11:55 nox wpa_supplicant[1360]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:11:55 nox wpa_supplicant[1360]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Apr 28 21:12:00 nox systemd-logind[1053]: Delay lock is active (UID 1000/portbound, PID 3434/gnome-shell) but inhibitor timeout is reached.
Apr 28 21:12:00 nox systemd[1]: Reached target sleep.target - Sleep.
Apr 28 21:12:00 nox systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 28 21:12:00 nox systemd[1]: [email protected]: Unit now frozen-by-parent.
Apr 28 21:12:00 nox systemd[1]: session-2.scope: Unit now frozen-by-parent.
Apr 28 21:12:00 nox systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 28 21:12:00 nox systemd[1]: user.slice: Unit now frozen.
Apr 28 21:12:00 nox systemd-sleep[9158]: Successfully froze unit 'user.slice'.
Apr 28 21:12:00 nox systemd-sleep[9158]: Performing sleep operation 'suspend'...
Apr 28 21:12:00 nox kernel: PM: suspend entry (s2idle)

Here's the output for a successful wakeup.

Apr 28 21:37:22 nox ModemManager[1116]: <msg> [sleep-monitor-systemd] system is about to suspend
Apr 28 21:37:22 nox ModemManager[1116]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.2471] manager: sleep: sleep requested (sleeping: no enabled: yes)
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.2475] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.2481] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.2483] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Apr 28 21:37:22 nox systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Apr 28 21:37:22 nox systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Apr 28 21:37:22 nox audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 28 21:37:22 nox kernel: wlp2s0: deauthenticating from 12:a7:93:fb:a1:ec by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 28 21:37:22 nox gnome-shell[3450]: Type GITypeInfo of property AccountsService.User:assword-mode does not match return type GITypeInfo of getter get_password_mode. Falling back to slow path
Apr 28 21:37:22 nox wpa_supplicant[1321]: nl80211: send_event_marker failed: Source based routing not supported
Apr 28 21:37:22 nox wpa_supplicant[1321]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=12:a7:93:fb:a1:ec reason=3 locally_generated=1
Apr 28 21:37:22 nox wpa_supplicant[1321]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5223] device (wlp2s0): supplicant interface state: completed -> disconnected
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5230] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Apr 28 21:37:22 nox avahi-daemon[995]: Withdrawing address record for 2600:8805:3d06::20fe on wlp2s0.
Apr 28 21:37:22 nox avahi-daemon[995]: Withdrawing address record for 2600:8805:3d06:0:66e2:2e2f:875b:a958 on wlp2s0.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5239] dhcp4 (wlp2s0): canceled DHCP transaction
Apr 28 21:37:22 nox avahi-daemon[995]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2600:8805:3d06:0:66e2:2e2f:875b:a958.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5239] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 28 21:37:22 nox avahi-daemon[995]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::aac0:34cf:e2f4:700.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5240] dhcp4 (wlp2s0): state changed no lease
Apr 28 21:37:22 nox avahi-daemon[995]: Registering new address record for fe80::aac0:34cf:e2f4:700 on wlp2s0.*.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5242] dhcp6 (wlp2s0): canceled DHCP transaction
Apr 28 21:37:22 nox avahi-daemon[995]: Withdrawing address record for fe80::aac0:34cf:e2f4:700 on wlp2s0.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5242] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 28 21:37:22 nox avahi-daemon[995]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::aac0:34cf:e2f4:700.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5242] dhcp6 (wlp2s0): state changed no lease
Apr 28 21:37:22 nox avahi-daemon[995]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Apr 28 21:37:22 nox audit[1119]: NETFILTER_CFG table=firewalld:8 family=1 entries=26 op=nft_unregister_rule pid=1119 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Apr 28 21:37:22 nox avahi-daemon[995]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 28 21:37:22 nox avahi-daemon[995]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:37:22 nox avahi-daemon[995]: Withdrawing address record for 192.168.0.83 on wlp2s0.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.5815] device (wlp2s0): set-hw-addr: set MAC address to 6A:19:AB:70:3D:44 (scanning)
Apr 28 21:37:22 nox avahi-daemon[995]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:37:22 nox avahi-daemon[995]: New relevant interface wlp2s0.IPv4 for mDNS.
Apr 28 21:37:22 nox avahi-daemon[995]: Registering new address record for 192.168.0.83 on wlp2s0.IPv4.
Apr 28 21:37:22 nox avahi-daemon[995]: Withdrawing address record for 192.168.0.83 on wlp2s0.
Apr 28 21:37:22 nox avahi-daemon[995]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.83.
Apr 28 21:37:22 nox avahi-daemon[995]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 28 21:37:22 nox systemd-resolved[962]: wlp2s0: Bus client set default route setting: no
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.6574] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.6579] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Apr 28 21:37:22 nox systemd-resolved[962]: wlp2s0: Bus client reset DNS server list.
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.6590] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 28 21:37:22 nox chronyd[1001]: Source 2001:470:b:22d::123 offline
Apr 28 21:37:22 nox chronyd[1001]: Source 2604:a880:1:20::17:5001 offline
Apr 28 21:37:22 nox chronyd[1001]: Source 23.155.72.147 offline
Apr 28 21:37:22 nox chronyd[1001]: Can't synchronise: no selectable sources (4 unreachable sources)
Apr 28 21:37:22 nox chronyd[1001]: Source 2607:7c80:54:3::56 offline
Apr 28 21:37:22 nox NetworkManager[1191]: <info> [1777426642.7043] device (wlp2s0): set-hw-addr: reset MAC address to 4C:23:38:48:FA:53 (unmanage)
Apr 28 21:37:22 nox geoclue[1752]: WiFi scan failed
Apr 28 21:37:22 nox wpa_supplicant[1321]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:37:22 nox wpa_supplicant[1321]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:37:22 nox wpa_supplicant[1321]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
Apr 28 21:37:22 nox wpa_supplicant[1321]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:37:22 nox wpa_supplicant[1321]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 28 21:37:22 nox wpa_supplicant[1321]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Apr 28 21:37:23 nox systemd[1]: Reached target sleep.target - Sleep.
Apr 28 21:37:23 nox systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 28 21:37:23 nox systemd[1]: session-2.scope: Unit now frozen-by-parent.
Apr 28 21:37:23 nox systemd[1]: [email protected]: Unit now frozen-by-parent.
Apr 28 21:37:23 nox systemd[1]: user.slice: Unit now frozen.
Apr 28 21:37:23 nox systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 28 21:37:23 nox systemd-sleep[5413]: Successfully froze unit 'user.slice'.
Apr 28 21:37:23 nox systemd-sleep[5413]: Performing sleep operation 'suspend'...
Apr 28 21:37:23 nox kernel: PM: suspend entry (s2idle)
Apr 28 21:37:23 nox kernel: Filesystems sync: 0.041 seconds
Apr 28 21:41:02 nox kernel: Freezing user space processes
Apr 28 21:41:02 nox systemd-resolved[962]: Clock change detected. Flushing caches.
Apr 28 21:41:02 nox rtkit-daemon[1007]: The canary thread is apparently starving. Taking action.
Apr 28 21:41:02 nox kernel: Freezing user space processes completed (elapsed 0.001 seconds)

Apr 28 21:41:02 nox systemd-logind[1032]: Lid opened.
Apr 28 21:41:02 nox rtkit-daemon[1007]: Demoting known real-time threads.
Apr 28 21:41:02 nox kernel: OOM killer disabled.
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3833 of process 3811 (/usr/bin/pipewire).
Apr 28 21:41:02 nox kernel: Freezing remaining freezable tasks
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3811 of process 3811 (/usr/bin/pipewire).
Apr 28 21:41:02 nox kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3483 of process 3450 (/usr/bin/gnome-shell).
Apr 28 21:41:02 nox kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3457 of process 3443 (/usr/bin/wireplumber).
Apr 28 21:41:02 nox kernel: queueing ieee80211 work while going to suspend
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3443 of process 3443 (/usr/bin/wireplumber).
Apr 28 21:41:02 nox kernel: PM: suspend devices took 0.090 seconds
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3447 of process 3442 (/usr/bin/pipewire).
Apr 28 21:41:02 nox kernel: ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are enabled
Apr 28 21:41:02 nox rtkit-daemon[1007]: Successfully demoted thread 3442 of process 3442 (/usr/bin/pipewire).
Apr 28 21:41:02 nox kernel: ACPI: EC: interrupt blocked
Apr 28 21:41:02 nox rtkit-daemon[1007]: Demoted 7 threads.
Apr 28 21:41:02 nox kernel: ACPI: EC: interrupt unblocked
Apr 28 21:41:02 nox kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: SMU is resuming...
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully!
Apr 28 21:41:02 nox kernel: nvme nvme0: 16/0/0 default/read/poll queues
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Apr 28 21:41:02 nox kernel: amdgpu 0000:05:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Apr 28 21:41:02 nox kernel: PM: resume devices took 0.219 seconds
Apr 28 21:41:02 nox kernel: OOM killer enabled.
Apr 28 21:41:02 nox kernel: Restarting tasks: Starting
Apr 28 21:41:02 nox kernel: Restarting tasks: Done
Apr 28 21:41:02 nox kernel: efivarfs: resyncing variable state
Apr 28 21:41:02 nox kernel: efivarfs: finished resyncing variable state
Apr 28 21:41:02 nox kernel: random: crng reseeded on system resumption
Apr 28 21:41:08 nox kernel: ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are enabled
Apr 28 21:41:08 nox systemd-sleep[5413]: System returned from sleep operation 'suspend'.
Apr 28 21:41:08 nox kernel: PM: suspend exit
Apr 28 21:41:08 nox bluetoothd[996]: Controller resume with wake event 0x0
Apr 28 21:41:08 nox systemd[1]: user.slice: Unit now thawed.
Apr 28 21:41:08 nox systemd[1]: user-1000.slice: Unit now thawed.
Apr 28 21:41:08 nox systemd-sleep[5413]: Successfully thawed unit 'user.slice'.
Apr 28 21:41:08 nox systemd[1]: [email protected]: Unit now thawed.
Apr 28 21:41:08 nox systemd[1]: session-2.scope: Unit now thawed.
Apr 28 21:41:08 nox systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 28 21:41:08 nox systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 28 21:41:08 nox audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 28 21:41:08 nox audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 28 21:41:08 nox systemd[1]: Stopped target sleep.target - Sleep.
Apr 28 21:41:08 nox systemd[1]: Reached target suspend.target - Suspend.
Apr 28 21:41:08 nox systemd-logind[1032]: Operation 'suspend' finished.
Apr 28 21:41:08 nox systemd-resolved[962]: Closing all remaining TCP connections.
Apr 28 21:41:08 nox ModemManager[1116]: <msg> [sleep-monitor-systemd] system is resuming

I'm not actually getting any meaningful output from journalctl when it fails since the last thing it logs is it's successful transition into s2. I tried to enable persistent logs via:

sudo mkdir -p /var/log/journal
sudo systemd-tmpfiles --create --prefix /var/log/journal

And then I restarted the service.

I have no clue what to even check at this point. I'd like to use GNOME because the gesture-based navigation is really nice on a 2-in-1, but failing to wake from suspend is a non-starter. Any guidance is appreciated!

 

[f33dm3bits]

I would report it to gnome-power-manager Gitlab repo and see what they say there.

GNOME / gnome-power-manager · GitLab

Welcome to GNOME GitLab

gitlab.gnome.org

 

[portbound]

Posted here: http://gitlab.gnome.org/GNOME/gnome-power-manager/-/work_items/35

 

[portbound]

Okay so I think I figured out what the issue is. Learned a lot along the way so here's the short version.

TLDR; there's a race condition occurring between gsd-power and the lid opening event notification that was causing a crash. It's not a GNOME issue, it's (probably) a firmware bug that GNOME exposed.
I was able to set the following arg in grubby, and reboot to fix it

sudo grubby --update-kernel=ALL --args="acpi_ec_no_wakeup=1"

➜ ~ sudo cat /sys/kernel/debug/suspend_stats
[sudo] password for portbound:
success: 14
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume_noirq: 0
failed_resume_early: 0
failed_resume: 0
failures:
last_failed_dev:

last_failed_errno: 0
0
last_failed_step:

yay

--
Here's more details in case anyone else comes across this:

Please excuse my lack of knowledge in this domain. This is not my wheelhouse and I was "today years old" when I learned what half of these terms meant. This is my rudimentary understanding of what was happening and how I was able to fix it.

Explanation:

The fact that journalctl just wasn't logging anything beyond the successful transition in s2 was really bothering me. It was kind of obvious it was happening upstream but I didn't really know how to capture that.

I read that I may need to try enabling pstore/ramoops to try and catch any kernel-level issues/panics. I did so via the following command and rebooted:

sudo grubby --update-kernel=ALL --args="ramoops.mem_address=0x8000000 ramoops.mem_size=0x200000 ramoops.ecc=1"

From what I understand about ramoops after having learned about it 5 hours ago, it's just a panic logger to try and catch failures beyond the threshold of a system crash.

The args I used are outlined here: https://mchehab.fedorapeople.org/kernel_docs/admin-guide/ramoops.html

Anyway, I was able to replicate the crash on wakeup again only to find that the logs were empty lol...

At this point I had no clue what was going on and assumed I was doing something wrong so I asked an LLM what was going on.

I usually don't like asking them about Linux related troubleshooting because their solution is usually just to throw everything but the kitchen sink at it. To the uninitiated, I'd generally advise caution here since it's pretty easy to jack up your system if you blindly copy commands or modify files you have no business modifying.

There was enough context here for the LLM to suggest that it may actually be a firmware/ACPI reset over a kernel panic, which would explain the lack of any meaningful logs.

So I checked the following:

sudo journalctl -b -1 -k | grep -iE "acpi|firmware"

And was met with:

Apr 29 14:56:18 nox kernel: ACPI Error: Thread 504246464 cannot release Mutex [ECMT] acquired by thread 226623488 (20250807/exmutex-378)

Apr 29 14:56:18 nox kernel: ACPI Error: Aborting method _SB.PCI0.LPC0.EC0.ECCC due to previous error (AE_AML_NOT_OWNER) (20250807/psparse-529)

Apr 29 14:56:18 nox kernel: ACPI Error: Aborting method _SB.PCI0.LPC0.EC0.RPAM due to previous error (AE_AML_NOT_OWNER) (20250807/psparse-529)

Apr 29 14:56:18 nox kernel: ACPI Error: Aborting method _SB.PCI0.LPC0.EC0._Q92 due to previous error (AE_AML_NOT_OWNER) (20250807/psparse-529)

Apparently the _Q92 EC event on Lenovo IdeaPads is a lid sensor notification, So this is where it was dying.

As I understand things, this is unfortunately the result of a couple factors.

GNOME is not what most would consider a lightweight DE. As an example, the gsd-power component is pretty active during the wakeup process. In particular gsd-power wakes up with the system and immediately tries to acquire the lock to do a bunch of hardware queries for things like getting the battery state, brightness levels, etc.

While gsd is holding the lock, the _Q92 event fires, and for whatever reason, doesn't respect the mutex's state and simply aborts when it can't proceed. In other words, someone probably forgot to add logic to acquire the lock before proceeding in this part of the firmware code.

So no, this is not a GNOME issue. GNOME just exposed a race condition that was already present in the firmware. That explains why lighter DE's weren't causing problems for me in my other configs.

 

[Condobloke]

Well done !