You are not logged in.

Pages: 1

#1 2025-04-03 03:42:25

Insouciant
Member
Registered: 2020-10-27
Posts: 8

[SOLVED]Wake from suspend fails occasionally and is seemingly erractic

=== Summary of Problem ===

I like to suspend my desktop when it's not in use, but it's a real coin toss as to whether it'll wake up successfully from sleep. It fails to wake from sleep around 30% of the time. This is what happens when it fails:

- I press a key on my keyboard to wake my PC.
- The power light goes from flashing to continuous (indicating that the computer is powered up)
- The fans spool up
- The keyboard comes on

THEN

- The keyboard goes off (backlight goes out) and stays off
- There is no display output:
    - On rare occasion there IS display output. I'll get nothing but the Breeze cursor on a black background.
- My system is completely unresponsive with no power to the keyboard.
- I am forced to hard reboot by pressing the hardware reboot button on my case.

=== System Information ===

Kernel: 6.13.8-arch1-1
DE: Plasma 6.3.3
Session: Wayland
CPU: AMD Ryzen 9 5900X
GPU: AMD ATI Radeon RX 7800 XT
Memory: 31991MiB

I've been tolerating this for months but I've finally resolved to have a good crack at fixing it. Journalctl yields some interesting results:

=== Logs ===

== Failed resume from suspend ==

 journalctl --boot=-1 | grep -A40 'The system will suspend now!' 
    Apr 02 22:53:13 zeus systemd-logind[2637]: The system will suspend now!
    Apr 02 22:53:13 zeus coolercontrold[2685]: System is going to sleep
    Apr 02 22:53:13 zeus NetworkManager[2635]: <info>  [1743587593.9421] manager: sleep: sleep requested (sleeping: no  enabled: yes)
    Apr 02 22:53:13 zeus NetworkManager[2635]: <info>  [1743587593.9422] manager: NetworkManager state is now ASLEEP
    Apr 02 22:53:13 zeus systemd[1]: Reached target Sleep.
    Apr 02 22:53:13 zeus systemd[1]: Starting System Suspend...
    Apr 02 22:53:13 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
    Apr 02 22:53:13 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
    Apr 02 22:53:13 zeus systemd[1]: user.slice: Unit now frozen.
    Apr 02 22:53:13 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
    Apr 02 22:53:13 zeus systemd-sleep[15984]: Successfully froze unit 'user.slice'.
    Apr 02 22:53:13 zeus systemd-sleep[15984]: Performing sleep operation 'suspend'...
    Apr 02 22:53:13 zeus kernel: PM: suspend entry (deep)

== Successful resume from suspend ==

 journalctl --boot | grep -A500 'The system will suspend now!' 
    Apr 03 16:14:27 zeus systemd-logind[2710]: The system will suspend now!
    Apr 03 16:14:27 zeus NetworkManager[2708]: <info>  [1743650067.5510] manager: sleep: sleep requested (sleeping: no  enabled: yes)
    Apr 03 16:14:27 zeus coolercontrold[2762]: System is going to sleep
    Apr 03 16:14:27 zeus NetworkManager[2708]: <info>  [1743650067.5511] manager: NetworkManager state is now ASLEEP
    Apr 03 16:14:27 zeus systemd[1]: Reached target Sleep.
    Apr 03 16:14:27 zeus systemd[1]: Starting System Suspend...
    Apr 03 16:14:27 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
    Apr 03 16:14:27 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
    Apr 03 16:14:27 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
    Apr 03 16:14:27 zeus systemd[1]: user.slice: Unit now frozen.
    Apr 03 16:14:27 zeus systemd-sleep[6696]: Successfully froze unit 'user.slice'.
    Apr 03 16:14:27 zeus systemd-sleep[6696]: Performing sleep operation 'suspend'...
    Apr 03 16:14:27 zeus kernel: PM: suspend entry (deep)
    Apr 03 16:14:27 zeus kernel: Filesystems sync: 0.020 seconds
    Apr 03 16:14:41 zeus kernel: Freezing user space processes
    Apr 03 16:14:41 zeus kernel: Freezing user space processes completed (elapsed 0.000 seconds)
    Apr 03 16:14:41 zeus kernel: OOM killer disabled.
    Apr 03 16:14:41 zeus kernel: Freezing remaining freezable tasks
    Apr 03 16:14:41 zeus kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
    Apr 03 16:14:41 zeus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
    Apr 03 16:14:41 zeus kernel: sd 3:0:0:0: [sda] Synchronizing SCSI cache
    Apr 03 16:14:41 zeus kernel: ata4.00: Entering standby power mode
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
    Apr 03 16:14:41 zeus kernel: ACPI: PM: Preparing to enter system sleep state S3
    Apr 03 16:14:41 zeus kernel: ACPI: PM: Saving platform NVS memory
    Apr 03 16:14:41 zeus kernel: Disabling non-boot CPUs ...
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 23 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 22 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 21 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 20 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 19 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 18 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 17 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 16 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 15 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 14 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 13 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 12 is now offline
    Apr 03 16:14:41 zeus kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 11 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 10 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 9 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 8 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 7 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 6 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 5 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 4 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 3 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 2 is now offline
    Apr 03 16:14:41 zeus kernel: smpboot: CPU 1 is now offline
    Apr 03 16:14:41 zeus kernel: ACPI: PM: Low-level resume complete
    Apr 03 16:14:41 zeus kernel: ACPI: PM: Restoring platform NVS memory
    Apr 03 16:14:41 zeus kernel: LVT offset 0 assigned for vector 0x400
    Apr 03 16:14:41 zeus kernel: Enabling non-boot CPUs ...
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
    Apr 03 16:14:41 zeus kernel: CPU1 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
    Apr 03 16:14:41 zeus kernel: CPU2 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
    Apr 03 16:14:41 zeus kernel: CPU3 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
    Apr 03 16:14:41 zeus kernel: CPU4 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
    Apr 03 16:14:41 zeus kernel: CPU5 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 6 APIC 0x10
    Apr 03 16:14:41 zeus kernel: CPU6 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 7 APIC 0x12
    Apr 03 16:14:41 zeus kernel: CPU7 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 8 APIC 0x14
    Apr 03 16:14:41 zeus kernel: CPU8 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 9 APIC 0x16
    Apr 03 16:14:41 zeus kernel: CPU9 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 10 APIC 0x18
    Apr 03 16:14:41 zeus kernel: CPU10 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 11 APIC 0x1a
    Apr 03 16:14:41 zeus kernel: CPU11 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 12 APIC 0x1
    Apr 03 16:14:41 zeus kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
    Apr 03 16:14:41 zeus kernel: CPU12 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 13 APIC 0x3
    Apr 03 16:14:41 zeus kernel: CPU13 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 14 APIC 0x5
    Apr 03 16:14:41 zeus kernel: CPU14 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 15 APIC 0x7
    Apr 03 16:14:41 zeus kernel: CPU15 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 16 APIC 0x9
    Apr 03 16:14:41 zeus kernel: CPU16 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 17 APIC 0xb
    Apr 03 16:14:41 zeus kernel: CPU17 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 18 APIC 0x11
    Apr 03 16:14:41 zeus kernel: CPU18 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 19 APIC 0x13
    Apr 03 16:14:41 zeus kernel: CPU19 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 20 APIC 0x15
    Apr 03 16:14:41 zeus kernel: CPU20 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 21 APIC 0x17
    Apr 03 16:14:41 zeus kernel: CPU21 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 22 APIC 0x19
    Apr 03 16:14:41 zeus kernel: CPU22 is up
    Apr 03 16:14:41 zeus kernel: smpboot: Booting Node 0 Processor 23 APIC 0x1b
    Apr 03 16:14:41 zeus kernel: CPU23 is up
    Apr 03 16:14:41 zeus kernel: ACPI: PM: Waking up from system sleep state S3
    Apr 03 16:14:41 zeus kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
    Apr 03 16:14:41 zeus kernel: usb usb1: root hub lost power or was reset
    Apr 03 16:14:41 zeus kernel: usb usb2: root hub lost power or was reset
    Apr 03 16:14:41 zeus kernel: nvme nvme0: D3 entry latency set to 8 seconds
    Apr 03 16:14:41 zeus kernel: nvme nvme1: 24/0/0 default/read/poll queues
    Apr 03 16:14:41 zeus kernel: nvme nvme0: 24/0/0 default/read/poll queues
    Apr 03 16:14:41 zeus kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008002000000).
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: PSP is resuming...
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: reserve 0xa700000 from 0x83e0000000 for PSP TMR
    Apr 03 16:14:41 zeus kernel: ata3: SATA link down (SStatus 0 SControl 300)
    Apr 03 16:14:41 zeus kernel: ata6: SATA link down (SStatus 0 SControl 330)
    Apr 03 16:14:41 zeus kernel: ata1: SATA link down (SStatus 0 SControl 330)
    Apr 03 16:14:41 zeus kernel: ata2: SATA link down (SStatus 0 SControl 330)
    Apr 03 16:14:41 zeus kernel: usb 1-7: reset high-speed USB device number 3 using xhci_hcd
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: RAP: optional rap ta ucode is not available
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resuming...
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00505300 (80.83.0)
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched
    Apr 03 16:14:41 zeus kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Apr 03 16:14:41 zeus kernel: sd 3:0:0:0: [sda] Starting disk
    Apr 03 16:14:41 zeus kernel: ata4.00: configured for UDMA/133
    Apr 03 16:14:41 zeus kernel: ahci 0000:02:00.1: port does not support device sleep
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resumed successfully!
    Apr 03 16:14:41 zeus kernel: [drm] DMUB hardware initialized: version=0x07002D00
    Apr 03 16:14:41 zeus kernel: usb 1-6: WARN: invalid context state for evaluate context command.
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
    Apr 03 16:14:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
    Apr 03 16:14:41 zeus kernel: [drm] ring gfx_32791.1.1 was added
    Apr 03 16:14:41 zeus kernel: [drm] ring compute_32791.2.2 was added
    Apr 03 16:14:41 zeus kernel: [drm] ring sdma_32791.3.3 was added
    Apr 03 16:14:41 zeus kernel: [drm] ring gfx_32791.1.1 ib test pass
    Apr 03 16:14:41 zeus kernel: [drm] ring compute_32791.2.2 ib test pass
    Apr 03 16:14:41 zeus kernel: [drm] ring sdma_32791.3.3 ib test pass
    Apr 03 16:14:41 zeus kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
    Apr 03 16:14:41 zeus kernel: usb 1-9: WARN: invalid context state for evaluate context command.
    Apr 03 16:14:41 zeus kernel: ata5: failed to resume link (SControl 0)
    Apr 03 16:14:41 zeus kernel: ata5: SATA link down (SStatus 0 SControl 0)
    Apr 03 16:14:41 zeus kernel: usb 1-9: reset full-speed USB device number 4 using xhci_hcd
    Apr 03 16:14:41 zeus kernel: OOM killer enabled.
    Apr 03 16:14:41 zeus kernel: Restarting tasks ... done.
    Apr 03 16:14:41 zeus kernel: random: crng reseeded on system resumption
    Apr 03 16:14:41 zeus kernel: PM: suspend exit
    Apr 03 16:14:41 zeus systemd-sleep[6696]: System returned from sleep operation 'suspend'.
    Apr 03 16:14:41 zeus systemd[1]: user.slice: Unit now thawed.
    Apr 03 16:14:41 zeus systemd[1]: user-1000.slice: Unit now thawed.
    Apr 03 16:14:41 zeus systemd-sleep[6696]: Successfully thawed unit 'user.slice'.
    Apr 03 16:14:41 zeus systemd[1]: session-1.scope: Unit now thawed.
    Apr 03 16:14:41 zeus systemd[1]: user@1000.service: Unit now thawed.
    Apr 03 16:14:41 zeus systemd[1]: systemd-suspend.service: Deactivated successfully.
    Apr 03 16:14:41 zeus systemd[1]: Finished System Suspend.
    Apr 03 16:14:41 zeus systemd[1]: Stopped target Sleep.
    Apr 03 16:14:41 zeus systemd[1]: Reached target Suspend.
    Apr 03 16:14:41 zeus systemd-logind[2710]: Operation 'suspend' finished.
    Apr 03 16:14:41 zeus systemd[1]: Stopped target Suspend.
    Apr 03 16:14:41 zeus coolercontrold[2762]: System is waking from sleep
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6546] manager: sleep: wake requested (sleeping: yes  enabled: yes)
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6546] device (enp7s0): state change: activated -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6547] dhcp4 (enp7s0): canceled DHCP transaction
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6547] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6547] dhcp4 (enp7s0): state changed no lease
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.6896] manager: NetworkManager state is now CONNECTED_GLOBAL
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.7374] manager: NetworkManager state is now DISCONNECTED
    Apr 03 16:14:41 zeus NetworkManager[2708]: <info>  [1743650081.7378] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
    Apr 03 16:14:41 zeus systemd[1]: Starting Network Manager Script Dispatcher Service...
    Apr 03 16:14:41 zeus systemd[1]: Started Network Manager Script Dispatcher Service.
    Apr 03 16:14:44 zeus coolercontrold[2762]: Re-initializing and re-applying settings after waking from sleep
    Apr 03 16:14:44 zeus coolercontrold[2762]: Applying all saved device settings
    Apr 03 16:14:44 zeus coolercontrold[2762]: Successfully applied:: nct6798 | fan1 |  Profile: Mix
    Apr 03 16:14:44 zeus coolercontrold[2762]: Successfully applied:: nct6798 | fan2 |  Profile: CPU Profile
    Apr 03 16:14:44 zeus coolercontrold[2762]: Successfully applied:: nct6798 | fan3 |  Profile: Mix
    Apr 03 16:14:44 zeus coolercontrold[2762]: Successfully applied:: nct6798 | fan4 |  Profile: Mix
    Apr 03 16:14:44 zeus coolercontrold[2762]: Successfully applied:: amdgpu | fan1 |  Profile: Default Profile
    Apr 03 16:14:44 zeus kernel: igc 0000:07:00.0 enp7s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6841] device (enp7s0): carrier: link connected
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6843] device (enp7s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6847] policy: auto-activating connection 'Wired connection 1' (0a4fe36c-8e58-314a-9a9b-8a61b57dd2f2)
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6849] device (enp7s0): Activation: starting connection 'Wired connection 1' (0a4fe36c-8e58-314a-9a9b-8a61b57dd2f2)
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6849] device (enp7s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6850] manager: NetworkManager state is now CONNECTING
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6851] device (enp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6855] device (enp7s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6857] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.6870] dhcp4 (enp7s0): state changed new lease, address=192.168.1.3, acd pending
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8593] dhcp4 (enp7s0): state changed new lease, address=192.168.1.3
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8598] policy: set 'Wired connection 1' (enp7s0) as default for IPv4 routing and DNS
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8775] device (enp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8782] device (enp7s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8783] device (enp7s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8785] manager: NetworkManager state is now CONNECTED_SITE
    Apr 03 16:14:44 zeus NetworkManager[2708]: <info>  [1743650084.8786] device (enp7s0): Activation: successful, device activated.
    Apr 03 16:14:45 zeus NetworkManager[2708]: <info>  [1743650085.4694] manager: NetworkManager state is now CONNECTED_GLOBAL
    Apr 03 16:14:51 zeus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    Apr 03 16:14:52 zeus kscreenlocker_greet[6665]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
    Apr 03 16:14:52 zeus kscreenlocker_greet[6665]: Failed to write to the pipe: Bad file descriptor.

In this very long journalctl log, you can see that the system is fully awake again by the line timestamped Apr 03 16:14:51 when the network dispatcher service finishes/deactivates.

Here's another journalctl entry from a different failed suspend operation

== Failed resume from suspend, example 2 ==

 journalctl --boot=-5 | grep -A40 'The system will suspend now!' 
    Mar 26 22:20:30 zeus systemd-logind[2638]: The system will suspend now!
    Mar 26 22:20:30 zeus coolercontrold[2687]: System is going to sleep
    Mar 26 22:20:30 zeus NetworkManager[2636]: <info>  [1742980830.2893] manager: sleep: sleep requested (sleeping: no  enabled: yes)
    Mar 26 22:20:30 zeus NetworkManager[2636]: <info>  [1742980830.2894] manager: NetworkManager state is now ASLEEP
    Mar 26 22:20:30 zeus systemd[1]: Reached target Sleep.
    Mar 26 22:20:30 zeus systemd[1]: Starting System Suspend...
    Mar 26 22:20:30 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
    Mar 26 22:20:30 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
    Mar 26 22:20:30 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
    Mar 26 22:20:30 zeus systemd[1]: user.slice: Unit now frozen.
    Mar 26 22:20:30 zeus systemd-sleep[8449]: Successfully froze unit 'user.slice'.
    Mar 26 22:20:30 zeus systemd-sleep[8449]: Performing sleep operation 'suspend'...
    Mar 26 22:20:30 zeus kernel: PM: suspend entry (deep)

As you can see, the final line here is the same as the first time. The system never makes it further than 'zeus kernel: PM: suspend entry (deep)'

I wondered if perhaps this had to do with my mkinitcpio configuration but I believe that is correct. I've used the same configuration on other comparable installs without issue. Here's the HOOKS section of my mkinitcpio:

 HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt filesystems fsck)

Here's an lsblk:

  [theo@zeus ~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda           8:0    0 931.5G  0 disk  
└─data      253:2    0 931.5G  0 crypt /mnt/data
zram0       252:0    0     4G  0 disk  [SWAP]
nvme1n1     259:0    0 476.9G  0 disk  
└─programs  253:1    0 476.9G  0 crypt /mnt/programs
nvme0n1     259:1    0 232.9G  0 disk  
├─nvme0n1p1 259:2    0     1G  0 part  /boot
└─nvme0n1p2 259:3    0 231.9G  0 part  
  └─root    253:0    0 231.9G  0 crypt /

As you can see my system is encrypted but I have not used lvm so there should be no need for the lvm2 hook. I also have not set up hibernation so there should be no need for the resume hook.

A super long post I know but I wanted to be informative. If anyone can help me I would be most grateful. Also if I've missed anything super obvious I'm sorry in advance.

Last edited by Insouciant (2025-05-22 21:33:01)

Offline

#2 2025-04-03 03:56:09

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

I just did four suspends in quick succession, the fourth of which failed with the same symptoms as described above. Again, when it fails, it's failing at the same stage:

[theo@zeus ~]$ journalctl --boot=-1 | grep -A40 'The system will suspend now!'
Apr 03 16:48:48 zeus systemd-logind[2636]: The system will suspend now!
Apr 03 16:48:48 zeus NetworkManager[2634]: <info>  [1743652128.7259] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 03 16:48:48 zeus coolercontrold[2682]: System is going to sleep
Apr 03 16:48:48 zeus NetworkManager[2634]: <info>  [1743652128.7260] manager: NetworkManager state is now ASLEEP
Apr 03 16:48:48 zeus systemd[1]: Reached target Sleep.
Apr 03 16:48:48 zeus systemd[1]: Starting System Suspend...
Apr 03 16:48:48 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 03 16:48:48 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
Apr 03 16:48:48 zeus systemd[1]: user.slice: Unit now frozen.
Apr 03 16:48:48 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 03 16:48:48 zeus systemd-sleep[4553]: Successfully froze unit 'user.slice'.
Apr 03 16:48:48 zeus systemd-sleep[4553]: Performing sleep operation 'suspend'...
Apr 03 16:48:48 zeus kernel: PM: suspend entry (deep)
Apr 03 16:48:55 zeus kernel: Filesystems sync: 1.109 seconds
Apr 03 16:48:55 zeus kernel: Freezing user space processes
Apr 03 16:48:55 zeus kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Apr 03 16:48:55 zeus kernel: OOM killer disabled.
Apr 03 16:48:55 zeus kernel: Freezing remaining freezable tasks
Apr 03 16:48:55 zeus kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Apr 03 16:48:55 zeus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 03 16:48:55 zeus kernel: sd 3:0:0:0: [sda] Synchronizing SCSI cache
Apr 03 16:48:55 zeus kernel: ata4.00: Entering standby power mode
Apr 03 16:48:55 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
Apr 03 16:48:55 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
Apr 03 16:48:55 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
Apr 03 16:48:55 zeus kernel: ACPI: PM: Preparing to enter system sleep state S3
Apr 03 16:48:55 zeus kernel: ACPI: PM: Saving platform NVS memory
Apr 03 16:48:55 zeus kernel: Disabling non-boot CPUs ...
Apr 03 16:48:55 zeus kernel: smpboot: CPU 23 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 22 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 21 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 20 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 19 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 18 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 17 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 16 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 15 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 14 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 13 is now offline
Apr 03 16:48:55 zeus kernel: smpboot: CPU 12 is now offline
Apr 03 16:48:55 zeus kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
--
Apr 03 16:49:05 zeus systemd-logind[2636]: The system will suspend now!
Apr 03 16:49:05 zeus coolercontrold[2682]: System is going to sleep
Apr 03 16:49:05 zeus NetworkManager[2634]: <info>  [1743652145.0172] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 03 16:49:05 zeus NetworkManager[2634]: <info>  [1743652145.0172] manager: NetworkManager state is now ASLEEP
Apr 03 16:49:05 zeus systemd[1]: Reached target Sleep.
Apr 03 16:49:05 zeus systemd[1]: Starting System Suspend...
Apr 03 16:49:05 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 03 16:49:05 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
Apr 03 16:49:05 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 03 16:49:05 zeus systemd[1]: user.slice: Unit now frozen.
Apr 03 16:49:05 zeus systemd-sleep[4813]: Successfully froze unit 'user.slice'.
Apr 03 16:49:05 zeus systemd-sleep[4813]: Performing sleep operation 'suspend'...
Apr 03 16:49:05 zeus kernel: PM: suspend entry (deep)
Apr 03 16:49:10 zeus kernel: Filesystems sync: 0.043 seconds
Apr 03 16:49:10 zeus kernel: Freezing user space processes
Apr 03 16:49:10 zeus kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Apr 03 16:49:10 zeus kernel: OOM killer disabled.
Apr 03 16:49:10 zeus kernel: Freezing remaining freezable tasks
Apr 03 16:49:10 zeus kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Apr 03 16:49:10 zeus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 03 16:49:10 zeus kernel: sd 3:0:0:0: [sda] Synchronizing SCSI cache
Apr 03 16:49:10 zeus kernel: ata4.00: Entering standby power mode
Apr 03 16:49:10 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
Apr 03 16:49:10 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
Apr 03 16:49:10 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
Apr 03 16:49:10 zeus kernel: ACPI: PM: Preparing to enter system sleep state S3
Apr 03 16:49:10 zeus kernel: ACPI: PM: Saving platform NVS memory
Apr 03 16:49:10 zeus kernel: Disabling non-boot CPUs ...
Apr 03 16:49:10 zeus kernel: smpboot: CPU 23 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 22 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 21 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 20 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 19 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 18 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 17 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 16 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 15 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 14 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 13 is now offline
Apr 03 16:49:10 zeus kernel: smpboot: CPU 12 is now offline
Apr 03 16:49:10 zeus kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
--
Apr 03 16:49:17 zeus systemd-logind[2636]: The system will suspend now!
Apr 03 16:49:17 zeus coolercontrold[2682]: System is going to sleep
Apr 03 16:49:17 zeus NetworkManager[2634]: <info>  [1743652157.0740] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 03 16:49:17 zeus NetworkManager[2634]: <info>  [1743652157.0740] manager: NetworkManager state is now ASLEEP
Apr 03 16:49:17 zeus systemd[1]: Reached target Sleep.
Apr 03 16:49:17 zeus systemd[1]: Starting System Suspend...
Apr 03 16:49:17 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 03 16:49:17 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
Apr 03 16:49:17 zeus systemd[1]: user.slice: Unit now frozen.
Apr 03 16:49:17 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 03 16:49:17 zeus systemd-sleep[4997]: Successfully froze unit 'user.slice'.
Apr 03 16:49:17 zeus systemd-sleep[4997]: Performing sleep operation 'suspend'...
Apr 03 16:49:17 zeus kernel: PM: suspend entry (deep)
Apr 03 16:49:17 zeus kernel: Filesystems sync: 0.047 seconds
Apr 03 16:49:41 zeus kernel: Freezing user space processes
Apr 03 16:49:41 zeus kernel: Freezing user space processes completed (elapsed 0.000 seconds)
Apr 03 16:49:41 zeus kernel: OOM killer disabled.
Apr 03 16:49:41 zeus kernel: Freezing remaining freezable tasks
Apr 03 16:49:41 zeus kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Apr 03 16:49:41 zeus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 03 16:49:41 zeus kernel: sd 3:0:0:0: [sda] Synchronizing SCSI cache
Apr 03 16:49:41 zeus kernel: ata4.00: Entering standby power mode
Apr 03 16:49:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
Apr 03 16:49:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
Apr 03 16:49:41 zeus kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
Apr 03 16:49:41 zeus kernel: ACPI: PM: Preparing to enter system sleep state S3
Apr 03 16:49:41 zeus kernel: ACPI: PM: Saving platform NVS memory
Apr 03 16:49:41 zeus kernel: Disabling non-boot CPUs ...
Apr 03 16:49:41 zeus kernel: smpboot: CPU 23 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 22 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 21 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 20 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 19 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 18 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 17 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 16 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 15 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 14 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 13 is now offline
Apr 03 16:49:41 zeus kernel: smpboot: CPU 12 is now offline
Apr 03 16:49:41 zeus kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
--
Apr 03 16:49:47 zeus systemd-logind[2636]: The system will suspend now!
Apr 03 16:49:47 zeus coolercontrold[2682]: System is going to sleep
Apr 03 16:49:47 zeus NetworkManager[2634]: <info>  [1743652187.4815] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 03 16:49:47 zeus NetworkManager[2634]: <info>  [1743652187.4816] manager: NetworkManager state is now ASLEEP
Apr 03 16:49:47 zeus systemd[1]: Reached target Sleep.
Apr 03 16:49:47 zeus systemd[1]: Starting System Suspend...
Apr 03 16:49:47 zeus systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 03 16:49:47 zeus systemd[1]: session-1.scope: Unit now frozen-by-parent.
Apr 03 16:49:47 zeus systemd[1]: user.slice: Unit now frozen.
Apr 03 16:49:47 zeus systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 03 16:49:47 zeus systemd-sleep[5110]: Successfully froze unit 'user.slice'.
Apr 03 16:49:47 zeus systemd-sleep[5110]: Performing sleep operation 'suspend'...
Apr 03 16:49:47 zeus kernel: PM: suspend entry (deep)
[theo@zeus ~]$

Last edited by Insouciant (2025-04-04 06:56:08)

Offline

#3 2025-04-03 14:51:45

seth
Member
Registered: 2012-09-03
Posts: 64,007

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Please use [code][/code] tags. Edit your post in this regard.

- I am forced to hard reboot by pressing the hardware reboot button on my case.

Avoid this under all circumstances.
· https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
· Short push on the power button (don't hold it)
· ssh ?

Usual suspects:
https://wiki.archlinux.org/title/Solid_ … leshooting
https://bbs.archlinux.org/viewtopic.php … 0#p2234980 (recent regression, might fit your black screen situation)
https://bbs.archlinux.org/viewtopic.php?id=296954

 Apr 03 16:14:41 zeus kernel: usb 1-6: WARN: invalid context state for evaluate context command.

What is that device?
Please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#4 2025-04-04 06:47:03

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Thanks for your quick response and numerous suggestions. I have added 

 kernel.sysrq = 0

to 

 /etc/sysctl.d/99-sysctl.conf

allowing me to use Alt+SysRq+b to reboot when this next happens. Or at least I can try and see if my system responds to this! I doubt it will however as my keyboard seems to lose power (lights go out).

As for SSH, I will also try this next time I encounter this scenario. As it only happens sometimes after resuming from suspend the issue may not crop up again for a while so this will likely be a slow burner of a fix.

As for those USB devices...

usb 1-6 is my keyboard (this is a USB 2.0 port)
As for usb 1-9 , I have no idea what this is. According to my motherboard manual, there shouldn't be a usb 1-9 so this is a bit odd.

Here's my complete system journal:

https://0x0.st/825W.txt

As for your list of usual suspects:

I looked through my full journalctl for nvme timeouts/device not ready. There is nothing there.

As for the post about AMDGPU drivers, I do not experience the same issues with the output of 

 lsmod | grep 7925
cat /proc/cmdline

as the OP does. I don't seem to have any issues with display output. The only issues I've experienced have been directly related to suspend and resume from suspend. But this is interesting for sure.

As for the third link, it seems this was likely resolved with a recent kernel update. I'm running kernel 6.13.8-arch1-1 so I'm probably okay with that issue. I also don't have a wireless card or any PCI devices.

Following some more reading I did this afternoon, I came across a few people who had mentioned issues with IOMMU so I set this to software mode by adding the kernel parameter 

 iommu=soft

I made this change too recently to be able to say whether or not it has fixed my issue.

Another consideration could be firmware/firmware updates for my two NVMe drives although seeing as I haven't been able to determine yet whether this is even an NVMe issue, I think this would be jumping the gun.

Offline

#5 2025-04-04 07:36:23

seth
Member
Registered: 2012-09-03
Posts: 64,007

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

allowing me to use Alt+SysRq+b to reboot when this next happens.

No, won't - you explicitly disabled it.

Apr 04 19:35:06 zeus kernel: ahci 0000:02:00.1: port does not support device sleep
Apr 04 19:35:06 zeus kernel: hid-generic 0003:0B05:1939.0001: hiddev96,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:02:00.0-6/input2
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.0/0003:04D9:A131.0002/input/input2
Apr 04 19:35:06 zeus kernel: hid-generic 0003:04D9:A131.0002: input,hidraw1: USB HID v1.11 Keyboard [HOLTEK USB-HID Keyboard] on usb-0000:02:00.0-9/input0
Apr 04 19:35:06 zeus kernel: hid-generic 0003:04D9:A131.0003: hiddev97,hidraw2: USB HID v1.11 Device [HOLTEK USB-HID Keyboard] on usb-0000:02:00.0-9/input1
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.2/0003:04D9:A131.0004/input/input4
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.2/0003:04D9:A131.0004/input/input5
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.2/0003:04D9:A131.0004/input/input6
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.2/0003:04D9:A131.0004/input/input7
Apr 04 19:35:06 zeus kernel: input: HOLTEK USB-HID Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-9/1-9:1.2/0003:04D9:A131.0004/input/input8

Plug that into a different hub.

Next to disabling the IOMMU please disable APST

The user session freeze hasn't been resolved at all by anything.
The problem is that it can cause issues for entirely different reasons, so in doubt disable that as well.

The posted journal does not include a (successful or not) attempt to sleep, one of the "I'll get nothing but the Breeze cursor on a black background." ones would be most interesting, since the system wakes up, but improperly.
It stands the best chance to indicate what's going wrong.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2025-04-04 10:20:06

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Sorry bad typo on my part. I meant to say that I added  

kernel.sysrq = 1

to 

  /etc/sysctl.d/99-sysctl.conf

, explicitly enabling SysRq.

Yup I'll try my keyboard in a different hub. I have it where it is (a USB 2.0) hub because I've prevented USB 3.0 from waking my machine, but still want to be able to wake my machine with my keyboard. I used the below script. I did this because my mouse (connected to a USB 3.0 port) would wake my system just by polling:

 /usr/lib/systemd/system-sleep/disable_usb_wake.sh 
 
#! /bin/bash
case $1 in
    pre)
        declare -a devices=(XHC0) # <-- Add your entries here

        for device in "${devices[@]}"; do
            if $(grep -qw ^${device}.*enabled /proc/acpi/wakeup); then
                echo ${device} > /proc/acpi/wakeup
            fi
        done
    ;;
esac

I wondered if this might have something to do with the suspend issue so I removed it for a while although the issue persisted so I don't think this is relevant. None the less I'll get rid of the script and have both my mouse and keyboard operating over USB 3.0 to further reduce complexity.

The last couple of times suspend/resume has failed, there has been no cursor so I have not been able to capture that yet.

As for disabling APST, I'd first like to know whether disabling IOMMU has had an effect. I haven't encountered a suspend/resume failure yet but it is still too early to say. APST is currently enabled for both of my NVME SSDs.

If and when I get another suspend/resume failure I'll take a photo if the cursor on black screen thing occurs and I'll then disable APST.

Eventually we should be able to narrow it down.

Thanks a bunch for your help so far.

Offline

#7 2025-05-01 07:38:11

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Hi Seth,

It has now been almost a month since my last post where I switched my keyboard over to my USB 3.0 hub (which cannot wake my machine thanks to the aforementioned script [disable_usb_wake.sh]) and moved to waking my computer only by pressing the power button . I can confirm that this issue has not returned .

As for why my machine fails to wake properly when a wake is triggered by my keyboard via my USB 2.0 hub, I do not know. I tried connecting my mouse to my USB 2.0 hub (usb 1-6), connecting my keyboard where my mouse was connected and then deleting 

  /usr/lib/systemd/system-sleep/disable_usb_wake.sh

This was not a viable solution as my mouse would keep waking my computer, presumably by polling. Instead of delving further into this issue, I simply swapped my mouse back to my USB 3.0 hub and re-instated disable_usb_wake.sh.

I am waking my computer via its power button and I am totally okay with that. It's barely an inconvenience. Maybe at some point in the future I'll stumble across something which will make me think of a solution, but for now let's park this and consider it solved.

Thank you for your help. You really pointed me in the right direction, particularly with your comment to try plugging my keyboard into a different hub.

PS: The SSD stuff was nothing but a wild goose chase. It had nothing to do with my SSD or APST or IOMMU.

Offline

#8 2025-05-01 13:52:39

seth
Member
Registered: 2012-09-03
Posts: 64,007

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

This was not a viable solution as my mouse would keep waking my computer, presumably by polling.

That's not normal.
Is it a wireless mouse (dongle)?
Sure the mouse doesn't flicker (the sensor doesn't decide on a spot, check "sudo evtest" or "sudo libinput debug events")
What happens if you just plug some usb key there (thumbdrive)?

It's barely an inconvenience.

Actually super easy? wink

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2025-05-05 21:40:51

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Actually super easy? wink

Hahaha. We're on the same page here!

Yes, I have a wireless mouse which uses a USB dongle. Other connected USB devices (including thumbdrives) do not wake my machine.

I'll investigate this issue further some time next week as I'm getting a new keyboard. I think it would be worth trying out waking my machine with a different keyboard to see if the original issue was caused by the keyboard itself, now that we know it's not an nvme SSD thing or some kernel-related issue.

I'll reply here once I've tested out my new keyboard. Ideally I don't want my mouse to wake my computer at all.

Offline

#10 2025-05-22 08:27:57

Insouciant
Member
Registered: 2020-10-27
Posts: 8

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Righto. So this is slightly embarrassing but it seems the issue was in fact my keyboard... I've had a different keyboard for the past couple of weeks now, still plugged into the same port (usb 1-6), and I have not experienced any issues resuming from suspend.

Another odd thing I've noticed is that the keyboard will sometimes wake the machine from suspend but more often than not it won't. I'll just have to press the power button. But I think we're getting into a different issue here and it's also just a minor inconvenience.

Really the first thing I should have tried is a different keyboard!

I'm sorry if you feel I've wasted your time and I am grateful for your support. This can be marked as solved and closed.

Last edited by Insouciant (2025-05-22 08:28:53)

Offline

#11 2025-05-22 14:29:32

seth
Member
Registered: 2012-09-03
Posts: 64,007

Re: [SOLVED]Wake from suspend fails occasionally and is seemingly erractic

Please mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB