You are not logged in.

#1 2026-07-12 19:39:52

pierreadame
Member
Registered: 2026-07-12
Posts: 4

Unresponsive after suspend (s2idle) ASUS ProArt PX13

My ASUS hybrid laptop doesn't wake from prolonged suspends (hour minimum or something like that).
I have to hard reset the laptop to get it to be responsive again.
It doesn't seem to leave any logs from crashing.
I have tried several different combinations of nvidia settings, I'm not sure they really did a lot.
Maybe it's lock utility related (since I don't think I've had this issue when unlocked, or at least the likelihood of it crashing is lower when unlocked, though Id prefer to have it locked).
I was using hyprlock, now I am using qylock (quickshell based).
I haven't done isolated testing since I am using the laptop actively at university, which makes it difficult to conduct troubleshooting.


$ journalctl --since="17:00" | rg -i suspend -C 30

lip 12 17:44:51 arch systemd-logind[799]: Lid closed.
lip 12 17:44:52 arch avahi-daemon[793]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::dab3:2fff:fe44:245d.
lip 12 17:44:52 arch avahi-daemon[793]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2001:67c:10ec:574c:8000::133e.
lip 12 17:44:52 arch avahi-daemon[793]: Registering new address record for 2001:67c:10ec:574c:8000::133e on wlan0.*.
lip 12 17:44:52 arch avahi-daemon[793]: Withdrawing address record for fe80::dab3:2fff:fe44:245d on wlan0.
lip 12 17:45:14 arch systemd-logind[799]: Suspending...
lip 12 17:45:14 arch rtkit-daemon[1103]: Demoting known real-time threads.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 124286 of process 120292.
lip 12 17:45:14 arch asusd[930]: [DEBUG asusd] Doing on_prepare_for_sleep(true)
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 52185 of process 51926.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 49124 of process 45209.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 2873 of process 2806.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 33499 of process 2022.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 2243 of process 2022.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1105 of process 1088.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1088 of process 1088.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1111 of process 1087.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1087 of process 1087.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1101 of process 1086.
lip 12 17:45:14 arch rtkit-daemon[1103]: Successfully demoted thread 1086 of process 1086.
lip 12 17:45:14 arch rtkit-daemon[1103]: Demoted 12 threads.
lip 12 17:45:14 arch systemd[1]: Starting Save keyboard backlight state before sleep...
lip 12 17:45:14 arch systemd[1]: Starting NVIDIA system suspend actions...
lip 12 17:45:14 arch suspend[197615]: nvidia-suspend.service
lip 12 17:45:14 arch logger[197615]: <13>Jul 12 17:45:14 suspend: nvidia-suspend.service
lip 12 17:45:14 arch systemd[1]: Finished Save keyboard backlight state before sleep.
lip 12 17:45:14 arch systemd[1]: Reached target Sleep.
lip 12 17:45:14 arch systemd[1]: nvidia-suspend.service: Deactivated successfully.
lip 12 17:45:14 arch systemd[1]: Finished NVIDIA system suspend actions.
lip 12 17:45:14 arch systemd[1]: Starting System Suspend...
lip 12 17:45:14 arch systemd-sleep[197622]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
lip 12 17:45:14 arch systemd-sleep[197622]: This is not recommended, and might result in unexpected behavior, particularly
lip 12 17:45:14 arch systemd-sleep[197622]: in suspend-then-hibernate operations or setups with encrypted home directories.
lip 12 17:45:14 arch systemd-sleep[197622]: Performing sleep operation 'suspend'...
lip 12 17:45:14 arch kernel: PM: suspend entry (s2idle)
-- Boot 6474e5b116f84753a63a30de6e37c0f0 --
lip 12 17:45:09 arch kernel: Linux version 7.1.3-arch1-2 (linux@archlinux) (gcc (GCC) 16.1.1 20260625, GNU ld (GNU Binutils) 2.46.1) #1 SMP PREEMPT_DYNAMIC Thu, 09 Jul 2026 19:55:55 +0000
lip 12 17:45:09 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=012ae0e8-2371-45d0-9225-aeb5e1357200 rw asus_nb_wmi.tablet_mode_sw=2 gpiolib_acpi.ignore_wake=ASCP1A00:00@8 pm_debug_messages log_buf_len=1M
lip 12 17:45:09 arch kernel: x86/split lock detection: #DB: warning on user-space bus_locks
lip 12 17:45:09 arch kernel: BIOS-provided physical RAM map:
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009b7efff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000009b7f000-0x0000000009ffffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a23bfff]  ACPI NVS
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000000a23c000-0x000000006817efff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000006817f000-0x000000006e17efff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000006e17f000-0x000000006e27efff]  ACPI data
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000006e27f000-0x000000007027efff]  ACPI NVS
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000007027f000-0x00000000783fefff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x00000000783ff000-0x0000000079ff6fff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000079ff7000-0x0000000079ffcfff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000079ffd000-0x0000000079ffefff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000079fff000-0x000000007bffffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [gap 0x000000007c000000-0x000000007d674fff]
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000007d675000-0x000000007d6fffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [gap 0x000000007d700000-0x000000007d7fffff]
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x000000007d800000-0x000000007fffffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [gap 0x0000000080000000-0x00000000dfffffff]
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [gap 0x00000000f0000000-0x00000000fcffffff]
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff]  device reserved
lip 12 17:45:09 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000085e17ffff]  System RAM
lip 12 17:45:09 arch kernel: BIOS-e820: [gap 0x000000085e180000-0x000000085f1bffff]
--
lip 12 17:45:09 arch kernel: pci 0000:00:08.2: PCI bridge to [bus c6]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.0: [1022:151f] type 00 class 0x0c0330 PCIe Endpoint
lip 12 17:45:09 arch kernel: pci 0000:c7:00.0: BAR 0 [mem 0xdde00000-0xddefffff 64bit]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.0: enabling Extended Tags
lip 12 17:45:09 arch kernel: pci 0000:c7:00.0: PME# supported from D0 D3hot D3cold
lip 12 17:45:09 arch kernel: pci 0000:c7:00.3: [1022:151a] type 00 class 0x0c0330 PCIe Endpoint
lip 12 17:45:09 arch kernel: pci 0000:c7:00.3: BAR 0 [mem 0xddd00000-0xdddfffff 64bit]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.3: enabling Extended Tags
lip 12 17:45:09 arch kernel: pci 0000:c7:00.3: PME# supported from D0 D3hot D3cold
lip 12 17:45:09 arch kernel: pci 0000:c7:00.4: [1022:151b] type 00 class 0x0c0330 PCIe Endpoint
lip 12 17:45:09 arch kernel: pci 0000:c7:00.4: BAR 0 [mem 0xddc00000-0xddcfffff 64bit]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.4: enabling Extended Tags
lip 12 17:45:09 arch kernel: pci 0000:c7:00.4: PME# supported from D0 D3hot D3cold
lip 12 17:45:09 arch kernel: pci 0000:c7:00.5: [1022:151c] type 00 class 0x0c0340 PCIe Endpoint
lip 12 17:45:09 arch kernel: pci 0000:c7:00.5: BAR 0 [mem 0xddf80000-0xddffffff 64bit]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.5: enabling Extended Tags
lip 12 17:45:09 arch kernel: pci 0000:c7:00.5: PME# supported from D0 D3hot D3cold
lip 12 17:45:09 arch kernel: pci 0000:c7:00.6: [1022:151d] type 00 class 0x0c0340 PCIe Endpoint
lip 12 17:45:09 arch kernel: pci 0000:c7:00.6: BAR 0 [mem 0xddf00000-0xddf7ffff 64bit]
lip 12 17:45:09 arch kernel: pci 0000:c7:00.6: enabling Extended Tags
lip 12 17:45:09 arch kernel: pci 0000:c7:00.6: PME# supported from D0 D3hot D3cold
lip 12 17:45:09 arch kernel: pci 0000:00:08.3: PCI bridge to [bus c7]
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
lip 12 17:45:09 arch kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
lip 12 17:45:09 arch kernel: Low-power S0 idle used by default for system suspend
lip 12 17:45:09 arch kernel: ACPI: EC: interrupt unblocked
lip 12 17:45:09 arch kernel: ACPI: EC: event unblocked
lip 12 17:45:09 arch kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
lip 12 17:45:09 arch kernel: ACPI: EC: GPE=0x10
lip 12 17:45:09 arch kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: Boot ECDT EC initialization complete
lip 12 17:45:09 arch kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: EC: Used to handle transactions and events
lip 12 17:45:09 arch kernel: iommu: Default domain type: Translated
lip 12 17:45:09 arch kernel: iommu: DMA domain TLB invalidation policy: lazy mode
lip 12 17:45:09 arch kernel: SCSI subsystem initialized
lip 12 17:45:09 arch kernel: libata version 3.00 loaded.
lip 12 17:45:09 arch kernel: ACPI: bus type USB registered
lip 12 17:45:09 arch kernel: usbcore: registered new interface driver usbfs
lip 12 17:45:09 arch kernel: usbcore: registered new interface driver hub
lip 12 17:45:09 arch kernel: usbcore: registered new device driver usb
lip 12 17:45:09 arch kernel: EDAC MC: Ver: 3.0.0
lip 12 17:45:09 arch kernel: efivars: Registered efivars operations
lip 12 17:45:09 arch kernel: NetLabel: Initializing
lip 12 17:45:09 arch kernel: NetLabel:  domain hash size = 128
lip 12 17:45:09 arch kernel: NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
lip 12 17:45:09 arch kernel: NetLabel:  unlabeled traffic allowed by default
lip 12 17:45:09 arch kernel: mctp: management component transport protocol core
lip 12 17:45:09 arch kernel: NET: Registered PF_MCTP protocol family
lip 12 17:45:09 arch kernel: PCI: Using ACPI for IRQ routing
lip 12 17:45:09 arch kernel: PCI: pci_cache_line_size set to 64 bytes
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x09b7f000-0x0bffffff]
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x0a200000-0x0bffffff]
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x60fb8000-0x63ffffff]
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x651dd000-0x67ffffff]
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x6817f000-0x6bffffff]
lip 12 17:45:09 arch kernel: e820: register RAM buffer resource [mem 0x79ff7000-0x7bffffff]
--
lip 12 17:45:09 arch kernel: usb 3-3: New USB device found, idVendor=0b05, idProduct=19b6, bcdDevice= 0.02
lip 12 17:45:09 arch kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
lip 12 17:45:09 arch kernel: usb 3-3: Product: N-KEY Device
lip 12 17:45:09 arch kernel: usb 3-3: Manufacturer: ASUSTeK Computer Inc.
lip 12 17:45:09 arch kernel: hid-sensor-hub 0003:3277:0059.0001: hiddev96,hidraw0: USB HID v1.11 Device [Shinetech ASUS FHD webcam] on usb-0000:c5:00.4-1/input4
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.0/0003:0B05:19B6.0002/input/input5
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device Consumer Control as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.0/0003:0B05:19B6.0002/input/input6
lip 12 17:45:09 arch kernel: [drm] [nvidia-drm] [GPU ID 0x0000c400] Loading driver
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.0/0003:0B05:19B6.0002/input/input7
lip 12 17:45:09 arch kernel: hid-generic 0003:0B05:19B6.0002: input,hiddev97,hidraw1: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input0
lip 12 17:45:09 arch kernel: hid-generic 0003:0B05:19B6.0003: hiddev98,hidraw2: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input1
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.2/0003:0B05:19B6.0004/input/input8
lip 12 17:45:09 arch kernel: hid-generic 0003:0B05:19B6.0004: input,hidraw3: USB HID v1.10 Keyboard [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input2
lip 12 17:45:09 arch kernel: asus 0003:0B05:19B6.0002: Fixing up Asus N-Key report descriptor
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.0/0003:0B05:19B6.0002/input/input9
lip 12 17:45:09 arch kernel: usb 3-5: new high-speed USB device number 3 using xhci_hcd
lip 12 17:45:09 arch kernel: asus 0003:0B05:19B6.0002: input,hiddev97,hidraw1: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input0
lip 12 17:45:09 arch kernel: asus 0003:0B05:19B6.0003: hiddev98,hidraw2: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input1
lip 12 17:45:09 arch kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.3/0000:c7:00.0/usb3/3-3/3-3:1.2/0003:0B05:19B6.0004/input/input10
lip 12 17:45:09 arch kernel: usb 3-5: New USB device found, idVendor=0489, idProduct=e11e, bcdDevice= 1.00
lip 12 17:45:09 arch kernel: usb 3-5: New USB device strings: Mfr=5, Product=6, SerialNumber=7
lip 12 17:45:09 arch kernel: usb 3-5: Product: Wireless_Device
lip 12 17:45:09 arch kernel: usb 3-5: Manufacturer: MediaTek Inc.
lip 12 17:45:09 arch kernel: usb 3-5: SerialNumber: 000000000
lip 12 17:45:09 arch kernel: asus 0003:0B05:19B6.0004: input,hidraw3: USB HID v1.10 Keyboard [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:c7:00.0-3/input2
lip 12 17:45:09 arch kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get target temp from SBIOS @ platform_request_handler_ctrl.c:2174
lip 12 17:45:09 arch kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get platform power mode from SBIOS @ platform_request_handler_ctrl.c:2117
lip 12 17:45:09 arch kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:c4:00.0 on minor 1
lip 12 17:45:09 arch kernel: nvidia 0000:c4:00.0: [drm] Cannot find any crtc or sizes
lip 12 17:45:09 arch kernel: Key type psk registered
lip 12 17:45:09 arch kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
lip 12 17:45:09 arch kernel: nvme nvme0: pci function 0000:c1:00.0
lip 12 17:45:09 arch kernel: nvme nvme0: passthrough uses implicit buffer lengths
lip 12 17:45:09 arch kernel: nvme nvme0: allocated 64 MiB host memory buffer (1 segment).
lip 12 17:45:09 arch kernel: nvme nvme0: 24/0/0 default/read/poll queues
lip 12 17:45:09 arch kernel:  nvme0n1: p1 p2 p3 p4 p5 p6 p7
lip 12 17:45:09 arch kernel: sdhci-pci 0000:c2:00.0: SDHCI controller found [17a0:9755] (rev 1)
lip 12 17:45:09 arch kernel: sdhci-pci 0000:c2:00.0: enabling device (0000 -> 0002)
lip 12 17:45:09 arch kernel: mmc0: SDHCI controller on PCI [0000:c2:00.0] using ADMA 64-bit
lip 12 17:45:09 arch kernel: amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GPPA.VGA_.ATPX handle
lip 12 17:45:09 arch kernel: amdgpu: ATPX version 1, functions 0x00000801
lip 12 17:45:09 arch kernel: amdgpu: ATPX Hybrid Graphics
lip 12 17:45:09 arch kernel: amdgpu: Virtual CRAT table created for CPU
lip 12 17:45:09 arch kernel: amdgpu: Topology: Add CPU node
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: enabling device (0006 -> 0007)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: initializing kernel modesetting (IP DISCOVERY 0x1002:0x150E 0x1043:0x38A8 0xC1).
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: register mmio base: 0xDD700000
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: register mmio size: 524288
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 0 <common_v1_0_0> (soc21_common)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 1 <gmc_v11_0_0> (gmc_v11_0)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 2 <ih_v6_0_0> (ih_v6_1)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 3 <psp_v13_0_0> (psp)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 4 <smu_v14_0_0> (smu)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 5 <dce_v1_0_0> (dm)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 6 <gfx_v11_0_0> (gfx_v11_0)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 7 <sdma_v6_0_0> (sdma_v6_0)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 8 <vcn_v4_0_5> (vcn_v4_0_5)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 9 <jpeg_v4_0_5> (jpeg_v4_0_5)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 10 <mes_v11_0_0> (mes_v11_0)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 11 <vpe_v6_1_0> (vpe_v6_1)
lip 12 17:45:09 arch kernel: amdgpu 0000:c5:00.0: detected ip block number 12 <isp_v4_1_0> (isp_ip)
--
lip 12 19:59:29 arch systemd[1447]: Listening on p11-kit server.
lip 12 19:59:29 arch systemd[1447]: Listening on PipeWire PulseAudio.
lip 12 19:59:29 arch systemd[1447]: Listening on PipeWire Multimedia System Sockets.
lip 12 19:59:29 arch systemd[1447]: Listening on Query the User Interactively for a Password.
lip 12 19:59:29 arch systemd[1447]: Listening on Disk Image Download Service Socket.
lip 12 19:59:29 arch systemd[1447]: Listening on Journal Log Access Socket.
lip 12 19:59:29 arch systemd[1447]: Listening on Virtual Machine and Container Registration Service Socket.
lip 12 19:59:29 arch systemd[1447]: Listening on Simple File System Backed Storage Provider.
lip 12 19:59:29 arch systemd[1447]: Listening on D-Bus User Message Bus Socket.
lip 12 19:59:29 arch systemd[1447]: Reached target Sockets.
lip 12 19:59:29 arch systemd[1447]: Starting D-Bus User Message Bus...
lip 12 19:59:29 arch dbus-broker-launch[1457]: Service file '/usr/share//dbus-1/services/nemo.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
lip 12 19:59:29 arch dbus-broker-launch[1457]: Service file '/usr/share//dbus-1/services/nemo.service' is not named after the D-Bus name 'org.Nemo'.
lip 12 19:59:29 arch dbus-broker-launch[1457]: Service file '/usr/share//dbus-1/services/org.erikreider.swaync.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
lip 12 19:59:29 arch dbus-broker-launch[1457]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.freedesktop.FileManager1.service'
lip 12 19:59:29 arch dbus-broker-launch[1457]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
lip 12 19:59:29 arch dbus-broker-launch[1457]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
lip 12 19:59:29 arch systemd[1447]: Started D-Bus User Message Bus.
lip 12 19:59:29 arch dbus-broker-launch[1457]: Ready
lip 12 19:59:29 arch systemd[1447]: Reached target Basic System.
lip 12 19:59:29 arch systemd[1]: Started User Manager for UID 1000.
lip 12 19:59:29 arch systemd[1447]: Started PipeWire Multimedia Service.
lip 12 19:59:29 arch systemd[1]: Started Session 1 of User piotradam.
lip 12 19:59:29 arch systemd[1447]: Started Multimedia Service Session Manager.
lip 12 19:59:29 arch systemd[1447]: Started PipeWire PulseAudio.
lip 12 19:59:29 arch login[955]: LOGIN ON tty1 BY piotradam
lip 12 19:59:29 arch systemd[1447]: Reached target Main User Target.
lip 12 19:59:29 arch systemd[1447]: Startup finished in 301ms.
lip 12 19:59:29 arch systemd[1]: Starting RealtimeKit Scheduling Policy Service...
lip 12 19:59:29 arch systemd[1]: Started RealtimeKit Scheduling Policy Service.
lip 12 19:59:29 arch rtkit-daemon[1471]: Handling system-suspend using logind.

Offline

#2 2026-07-12 20:29:57

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,833

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

It doesn't seem to leave any logs from crashing.

Even if it does wake up

I have to hard reset the laptop to get it to be responsive again.

would prevent the journal from being synced to disk

https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Until then let's just throw stuff against the wall:
Are you running on amdgpu or nvidia? (There's no output attached to the nvidia GPU) - can you deactivate either chip in the UEFI settings?

nvme0n1: p1 p2 p3 p4 p5 p6 p7

1. parallel windows? see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
2. https://wiki.archlinux.org/title/Solid_ … leshooting

nvme_core.default_ps_max_latency_us=0  pcie_aspm=off iommu=soft

Online

#3 2026-07-13 09:38:31

pierreadame
Member
Registered: 2026-07-12
Posts: 4

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

I did the REISUB sequence but still nothing

$ journalctl --since="9:00" | rg -i suspend -C 20
lip 13 09:19:06 arch systemd-logind[57614]: Lid closed.
lip 13 09:19:06 arch systemd-logind[57614]: Suspending...
lip 13 09:19:06 arch rtkit-daemon[57816]: Demoting known real-time threads.
lip 13 09:19:06 arch asusd[85092]: [DEBUG asusd] Doing on_prepare_for_sleep(true)
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 61889 of process 61819.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 82601 of process 60742.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 60966 of process 60742.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57828 of process 57802.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57802 of process 57802.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57811 of process 57801.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57801 of process 57801.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57822 of process 57803.
lip 13 09:19:06 arch rtkit-daemon[57816]: Successfully demoted thread 57803 of process 57803.
lip 13 09:19:06 arch rtkit-daemon[57816]: Demoted 9 threads.
lip 13 09:19:06 arch systemd[1]: Starting Save keyboard backlight state before sleep...
lip 13 09:19:06 arch systemd[1]: Starting NVIDIA system suspend actions...
lip 13 09:19:06 arch suspend[110191]: nvidia-suspend.service
lip 13 09:19:06 arch logger[110191]: <13>Jul 13 09:19:06 suspend: nvidia-suspend.service
lip 13 09:19:06 arch systemd[1]: Finished Save keyboard backlight state before sleep.
lip 13 09:19:06 arch systemd[1]: Reached target Sleep.
lip 13 09:19:06 arch systemd[1]: nvidia-suspend.service: Deactivated successfully.
lip 13 09:19:06 arch systemd[1]: Finished NVIDIA system suspend actions.
lip 13 09:19:06 arch systemd[1]: Starting System Suspend...
lip 13 09:19:06 arch systemd-sleep[110197]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
lip 13 09:19:06 arch systemd-sleep[110197]: This is not recommended, and might result in unexpected behavior, particularly
lip 13 09:19:06 arch systemd-sleep[110197]: in suspend-then-hibernate operations or setups with encrypted home directories.
lip 13 09:19:06 arch systemd-sleep[110197]: Performing sleep operation 'suspend'...
lip 13 09:19:06 arch kernel: PM: suspend entry (s2idle)
-- Boot 89460243efdb4268aa61b3dc6c65bf74 --
lip 13 11:08:50 arch kernel: Linux version 7.1.3-arch1-2 (linux@archlinux) (gcc (GCC) 16.1.1 20260625, GNU ld (GNU Binutils) 2.46.1) #1 SMP PREEMPT_DYNAMIC Thu, 09 Jul 2026 19:55:55 +0000
lip 13 11:08:50 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=012ae0e8-2371-45d0-9225-aeb5e1357200 rw asus_nb_wmi.tablet_mode_sw=2
lip 13 11:08:50 arch kernel: x86/split lock detection: #DB: warning on user-space bus_locks
lip 13 11:08:50 arch kernel: BIOS-provided physical RAM map:
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff]  device reserved
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009b7efff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000009b7f000-0x0000000009ffffff]  device reserved
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a23bfff]  ACPI NVS
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000000a23c000-0x000000006817efff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000006817f000-0x000000006e17efff]  device reserved
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000006e17f000-0x000000006e27efff]  ACPI data
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000006e27f000-0x000000007027efff]  ACPI NVS
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x000000007027f000-0x00000000783fefff]  device reserved
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x00000000783ff000-0x0000000079ff6fff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000079ff7000-0x0000000079ffcfff]  device reserved
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000079ffd000-0x0000000079ffefff]  System RAM
lip 13 11:08:50 arch kernel: BIOS-e820: [mem 0x0000000079fff000-0x000000007bffffff]  device reserved

This was without

nvme_core.default_ps_max_latency_us=0  pcie_aspm=off iommu=soft

I've added them now and will report whether they seem to help or not.
I've had fast start disabled for a long time already.
I haven't seen any option to disable either gpu in the uefi settings.
I am mainly using the amdgpu for power consumption reasons (the nvidia card is only used for 3d rendering and that sort of thing with prime offloading).


$ cat etc/systemd/sleep.conf
[Sleep]
AllowSuspend=yes
AllowHibernation=no
AllowSuspendThenHibernate=no
#AllowHybridSleep=yes
#SuspendState=mem standby freeze
SuspendState=freeze
#HibernateMode=platform shutdown
#MemorySleepMode=deep
#HibernateDelaySec=
#HibernateOnACPower=yes
#SuspendEstimationSec=60min
$ cat /proc/driver/nvidia/params
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
InitializeSystemMemoryAllocations: 1
EnableMSI: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 2
UseKernelSuspendNotifiers: 1
EnableS0ixPowerManagement: 0
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
TegraGpuPgMask: 0
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableResizableBar: 0
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2
RmNvlinkBandwidthLinkCount: 0
EnableDbgBreakpoint: 0
OpenRmEnableUnsupportedGpus: 1
DmaRemapPeerMmio: 1
ImexChannelCount: 2048
CreateImexChannel0: 0
EnableSystemMemoryPools: 529
OsEnableCxlSupport: 1
EnableDebuggerInterface: 0
CoherentGPUMemoryMode: "numa"
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/var/tmp"
ExcludedGpus: ""

Offline

#4 2026-07-13 10:24:40

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,833

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

I did the REISUB sequence but still nothing

If it did reboot the system that means the kernel resumed - the loss of the journal then would implicate the nvme not waking up.

I've had fast start disabled for a long time already.

Make sure it still is - windows habitually re-enables it with updates.

Online

#5 2026-07-13 10:40:27

pierreadame
Member
Registered: 2026-07-12
Posts: 4

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

No it didn't reboot the system. The laptop remained unresponsive. Fasst start is still disabled.

Offline

#6 2026-07-13 10:55:07

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,833

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

You did explicitly enable the sysrq resp. it works when not failing to wake up?

Online

#7 2026-07-13 11:02:39

pierreadame
Member
Registered: 2026-07-12
Posts: 4

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

Yes sysrq works. When I press alt + printscrn + E right now Hyprland and everything quits and I am in tty.

Offline

#8 2026-07-13 18:48:54

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,833

Re: Unresponsive after suspend (s2idle) ASUS ProArt PX13

Is this a regression?
https://bbs.archlinux.org/viewtopic.php?id=314191

(The nvme might still be at play here, there's just no longer a strong indication for this)

Online

Board footer

Powered by FluxBB