[Solved] Resume immediately after suspend

KylinDemons · 2025-06-20 07:28:29

When I try to suspend my laptop, it resumes immediately after the laptop screen goes black and the sleep indicator light flashes once.

I got these information about dmesg:

[  166.475088] PM: suspend entry (s2idle)
[  166.523716] Filesystems sync: 0.048 seconds
[  166.590525] Freezing user space processes
[  166.591962] Freezing user space processes completed (elapsed 0.001 seconds)
[  166.591964] OOM killer disabled.
[  166.591965] Freezing remaining freezable tasks
[  166.593075] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  166.593076] printk: Suspending console(s) (use no_console_suspend to debug)
[  170.721904] spd5118 12-0050: Failed to write b = 0: -6
[  170.721907] spd5118 12-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[  170.721915] spd5118 12-0050: PM: failed to resume async: error -6
[  170.722068] spd5118 12-0052: Failed to write b = 0: -6
[  170.722069] spd5118 12-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[  170.722070] spd5118 12-0052: PM: failed to resume async: error -6
[  170.727938] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.44.1
[  170.727943] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[  170.745187] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
[  170.746108] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[  170.746109] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[  170.746596] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[  171.105913] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[  171.106945] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[  171.107552] OOM killer enabled.
[  171.107554] Restarting tasks ... done.
[  171.108936] random: crng reseeded on system resumption
[  171.111745] PM: suspend exit

From the logs, it appears the spd5118 module might be involved, but after searching, its error messages seem non-critical (or possibly irrelevant?).

My laptop (ASUS TUF Gaming F15 FX507VV) only supports S0ix (s2idle) suspend mode. While the system explicitly claims support for deep sleep, forcing it (e.g., via deep in /sys/power/mem_sleep) causes an immediate shutdown instead of suspending.

Hibernation (suspend-to-disk) works normally.
Both suspend and hibernation function correctly under Windows.

Hardware:
CPU: 13th Gen Intel® Core™ i9-13900H
RAM: 64GB DDR5 5200MHz
GPU: NVIDIA RTX 4060 Laptop (using nvidia-open driver)
BIOS: American Megatrends International, LLC. FX507VV.329

Has anyone resolved similar suspend issue?
Or are there known workarounds for deep sleep working properly instead of using S0ix？

Last edited by KylinDemons (2025-06-23 02:48:33)

seth · 2025-06-20 08:39:12

Please post the system journal for userspace context, spd5118 is a thermal sensor, you could try to blacklist it to see whether it's relevant.

KylinDemons · 2025-06-20 10:51:23

seth wrote:

Please post the system journal for userspace context, spd5118 is a thermal sensor, you could try to blacklist it to see whether it's relevant.

Here is the system journal for userspace:

6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV systemd-logind[664]: The system will suspend now!
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.5174] manager: sleep: sleep requested (sleeping: no  enabled: yes)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.5175] device (enp55s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV dbus-broker[660]: A security policy denied :1.35 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV kwin_wayland[895]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV dbus-broker[660]: A security policy denied :1.35 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV kwin_wayland[895]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.5242] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.5245] manager: NetworkManager state is now ASLEEP
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.5247] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Starting Network Manager Script Dispatcher Service...
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Started Network Manager Script Dispatcher Service.
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV kernel: wlan0: deauthenticating from dc:d8:7b:5d:46:f8 by local choice (Reason: 3=DEAUTH_LEAVING)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: nl80211: send_event_marker failed: Source based routing not supported
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: wlan0: CTRL-EVENT-DISCONNECTED bssid=dc:d8:7b:5d:46:f8 reason=3 locally_generated=1
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6668] device (wlan0): supplicant interface state: completed -> disconnected
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6669] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6670] dhcp4 (wlan0): canceled DHCP transaction
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6670] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6671] dhcp4 (wlan0): state changed no lease
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6671] dhcp6 (wlan0): canceled DHCP transaction
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6671] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6671] dhcp6 (wlan0): state changed no lease
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: wlan0: PMKSA-CACHE-REMOVED dc:d8:7b:5d:46:f8 0
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.6868] device (wlan0): set-hw-addr: set MAC address to CE:CB:4D:93:80:26 (scanning)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.7246] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416300.8533] device (wlan0): set-hw-addr: reset MAC address to F4:C8:8A:4D:6B:65 (unmanage)
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV wpa_supplicant[734]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Reached target Sleep.
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Starting NVIDIA system suspend actions...
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV suspend[27497]: nvidia-suspend.service
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV logger[27497]: <13>Jun 20 18:45:00 suspend: nvidia-suspend.service
6月 20 18:45:00 ASUS-TUF-Gaming-F15-FX507VV kscreenlocker_greet[27462]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:100: TypeError: Cannot read property 'description' of undefined
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:100: TypeError: Cannot read property 'description' of undefined
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "auto_null.monitor"
6月 20 18:45:01 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "auto_null.monitor"
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: nvidia-suspend.service: Deactivated successfully.
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Finished NVIDIA system suspend actions.
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Starting System Suspend...
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd-sleep[27538]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd-sleep[27538]: This is not recommended, and might result in unexpected behavior, particularly
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd-sleep[27538]: in suspend-then-hibernate operations or setups with encrypted home directories.
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV systemd-sleep[27538]: Performing sleep operation 'suspend'...
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV kernel: PM: suspend entry (s2idle)
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV kernel: Filesystems sync: 0.018 seconds
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing user space processes
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing user space processes completed (elapsed 0.001 seconds)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: OOM killer disabled.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing remaining freezable tasks
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: printk: Suspending console(s) (use no_console_suspend to debug)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: Failed to write b = 0: -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: PM: failed to resume async: error -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: Failed to write b = 0: -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: PM: failed to resume async: error -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.44.1
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: OOM killer enabled.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Restarting tasks ... 
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: done.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: random: crng reseeded on system resumption
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: PM: suspend exit
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV systemd-sleep[27538]: System returned from sleep operation 'suspend'.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kernel: nvidia-modeset: nvidia-modeset: ACPI reported no NVIDIA native backlight available; attempting to use ACPI backlight.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: systemd-suspend.service: Deactivated successfully.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Finished System Suspend.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Stopped target Sleep.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Reached target Suspend.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd-logind[664]: Operation 'suspend' finished.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416308.3542] manager: sleep: wake requested (sleeping: yes  enabled: yes)
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV NetworkManager[661]: <info>  [1750416308.3543] device (enp55s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Starting NVIDIA system resume actions...
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Stopped target Suspend.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV suspend[27649]: nvidia-resume.service
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV logger[27649]: <13>Jun 20 18:45:08 suspend: nvidia-resume.service
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: nvidia-resume.service: Deactivated successfully.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV systemd[1]: Finished NVIDIA system resume actions.
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kernel: Generic FE-GE Realtek PHY r8169-0-3700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-3700:00, irq=MAC)
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV wireplumber[837]: spa.bluez5: BlueZ system service is not available
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "auto_null"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "auto_null.monitor"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "auto_null"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "auto_null.monitor"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kded6[1028]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV plasmashell[1063]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
6月 20 18:45:08 ASUS-TUF-Gaming-F15-FX507VV kernel: r8169 0000:37:00.0 enp55s0: Link is Down

seth · 2025-06-20 15:45:12

6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV kernel: PM: suspend entry (s2idle)
6月 20 18:45:03 ASUS-TUF-Gaming-F15-FX507VV kernel: Filesystems sync: 0.018 seconds
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing user space processes
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing user space processes completed (elapsed 0.001 seconds)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: OOM killer disabled.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing remaining freezable tasks
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: printk: Suspending console(s) (use no_console_suspend to debug)
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: Failed to write b = 0: -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0050: PM: failed to resume async: error -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: Failed to write b = 0: -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: spd5118 12-0052: PM: failed to resume async: error -6
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.44.1
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: OOM killer enabled.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: Restarting tasks ... 
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: done.
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: random: crng reseeded on system resumption
6月 20 18:45:07 ASUS-TUF-Gaming-F15-FX507VV kernel: PM: suspend exit

If it's not spd5118 (tried to blacklist it?) it's either a hibernating windows (do you run a dual boot system?) or spurious wakeup trigger

cat /proc/acpi/wakeup

KylinDemons · 2025-06-23 02:47:27

I have figured it out. It's XHCI.

I write a systemd unit to solve this problem.

sudo tee /etc/systemd/system/disable-wakeup.service <<EOF
[Unit]
Description=Disable XHCI Wakeup
Before=sleep.target

[Service]
Type=oneshot
ExecStart=/bin/sh -c 'echo XHCI > /proc/acpi/wakeup'
ExecStop=/bin/sh -c 'echo XHCI > /proc/acpi/wakeup'
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl enable --now disable-wakeup.service

seth · 2025-06-23 06:14:56

That's usb. Some suspicious external device plugged in?

lsusb -tv

KylinDemons · 2025-06-23 06:57:16

seth wrote:

That's usb. Some suspicious external device plugged in?
lsusb -tv

Nop. That's exactly the strange thing, I didn't even consider it was USB controller. I once searched for Asus laptops on the forum about USB controllers waking up sleep, but I didn't take it seriously. This may be some firmware bug.
Anyway, thank you!!

seth · 2025-06-23 07:23:44

So… some internal device?
What's on the bus? Eg. a fingerprint reader? With mild fat stains?

Arch Linux

#1 2025-06-20 07:28:29

[Solved] Resume immediately after suspend

#2 2025-06-20 08:39:12

Re: [Solved] Resume immediately after suspend

#3 2025-06-20 10:51:23

Re: [Solved] Resume immediately after suspend

#4 2025-06-20 15:45:12

Re: [Solved] Resume immediately after suspend

#5 2025-06-23 02:47:27

Re: [Solved] Resume immediately after suspend

#6 2025-06-23 06:14:56

Re: [Solved] Resume immediately after suspend

#7 2025-06-23 06:57:16

Re: [Solved] Resume immediately after suspend

#8 2025-06-23 07:23:44

Re: [Solved] Resume immediately after suspend

Board footer