Hi,
can you help me debug the problem?
There is asus nuc 16 pro with fresh installation of openSuse TW + KDE.
When I press sleep button or systemctl suspend the screen goes dark and after about 10sec the system reloads. I don’t have swap partition or swap file, I want to suspend-to-RAM, not hibernate
cat /sys/power/mem_sleep
s2idle [deep]
journalctl -b -1
nov 05 05:00:05 systemd-logind[985]: suspend requested from client PID 2438 ('org_kde_powerde') (unit user@1000.service)...
nov 05 05:00:05 rtkit-daemon[2233]: Demoting known real-time threads.
nov 05 05:00:05 systemd-logind[985]: The system will suspend now!
nov 05 05:00:05 org_kde_powerdevil[2438]: Watching for display connection changes, resolved watch mode = Watch_Mode_Udev, poll loop interval = 500 millisec
nov 05 05:00:05 org_kde_powerdevil[2438]: initial_stabilization_millisec: 0, stabilization_poll_millisec: 100
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 5858 of process 5393.
nov 05 05:00:05 NetworkManager[1202]: <info> [1793851205.9285] manager: sleep: sleep requested (sleeping: no enabled: yes)
nov 05 05:00:05 ModemManager[1082]: <msg> [sleep-monitor-systemd] system is about to suspend
nov 05 05:00:05 NetworkManager[1202]: <info> [1793851205.9313] device (wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 5825 of process 2625.
nov 05 05:00:05 NetworkManager[1202]: <info> [1793851205.9325] device (wlo1): set-hw-addr: reset MAC address to 54:AD:B0:18:C5:B2 (unmanage)
nov 05 05:00:05 org_kde_powerdevil[2438]: [ 2473][3110.031403] (ldbus_handle_message)Received dbus signal PrepareForSleep(true=prepare)
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 5634 of process 2625.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 14106 of process 2622.
nov 05 05:00:05 ModemManager[1082]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 4785 of process 2622.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 3061 of process 2716.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2290 of process 2285.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2285 of process 2285.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2229 of process 2219.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2219 of process 2219.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2234 of process 2220.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2239 of process 2220.
nov 05 05:00:05 rtkit-daemon[2233]: Successfully demoted thread 2220 of process 2220.
nov 05 05:00:05 NetworkManager[1202]: <info> [1793851205.9357] manager: NetworkManager state is now DISABLED (ASLEEP)
nov 05 05:00:05 rtkit-daemon[2233]: Demoted 13 threads.
nov 05 05:00:05 google-chrome-stable[2712]: [2687:2907:1105/050005.938973:ERROR:google_apis/gcm/engine/connection_factory_impl.cc:474] ConnectionHandler failed with net error: -2
nov 05 05:00:05 systemd[1]: Starting PackageKit Daemon...
nov 05 05:00:05 systemd-logind[985]: Suspend key pressed short.
nov 05 05:00:06 PackageKit[14260]: daemon start
nov 05 05:00:06 systemd[1]: Starting DBus interface for snapper...
nov 05 05:00:06 systemd[1]: Started PackageKit Daemon.
nov 05 05:00:06 systemd[1]: Started DBus interface for snapper.
nov 05 05:00:06 systemd-helper[14255]: Running cleanup for 'root'.
nov 05 05:00:06 systemd[1]: snapper-timeline.service: Deactivated successfully.
nov 05 05:00:06 systemd-helper[14255]: Running number cleanup for 'root'.
nov 05 05:00:06 systemd-helper[14255]: Deleting snapshot from root:
nov 05 05:00:06 systemd-helper[14255]: 113
nov 05 05:00:06 systemd[1]: Reached target Sleep.
nov 05 05:00:06 systemd[1]: Starting System Suspend...
nov 05 05:00:06 systemd[1]: session-3.scope: Unit now frozen-by-parent.
nov 05 05:00:06 systemd[1]: user.slice: Unit now frozen.
nov 05 05:00:06 systemd[1]: user-1000.slice: Unit now frozen-by-parent.
nov 05 05:00:06 systemd[1]: user@1000.service: Unit now frozen-by-parent.
nov 05 05:00:06 systemd-sleep[14319]: Successfully froze unit 'user.slice'.
nov 05 05:00:06 systemd-sleep[14319]: Performing sleep operation 'suspend'...
nov 05 05:00:06 kernel: PM: suspend entry (deep)
Modern Intel platforms don’t play nicely with S3 (Suspend-to-RAM) having deprecated it in favor of S0ix (Modern Standby). You can check in the BIOS to see if there is a setting to enable S3 support, but if not, you will want to use s2idle instead of deep.
I haven’t seen any S3 setting in Bios, only S4/S5 s2idle doesn’t work for me either - the PC sort of sleeps, the fans are out, but something is still running in OS, when I wake it up, I see temperatures 70+ degrees
To add: on my ThinkPad P162 Gen2 I was suspicious too, but
a USB connected phone would send signals to USB, so unplugged that assuming it might wake the machine up
I completely misjudged the wake up time. If I open the lid the screenlocker is instantly there. Needed to run the above command to actually confirm that it did go to sleep.
I’ve seen more people having similar issues. Mostly disconnecting or moving to a different USB port of powered USB hubs got it to work. But that is sort of shooting in the dark.
That was going to be my next guess. I know all too well the problems certain wireless receivers can cause…
That sounds an awful lot like interrupted modern standby. Modern standby is a lot more reliant on driver compliance than suspend-to-RAM, so if some USB or PCIe device doesn’t comply with the suspend, it can cause problems.
My new PC would always crash when entering suspend until I pinpointed my Logitech wireless receiver as the culprit.
As @knurpht suggested, more complete log files would help.
in my particular case, i had lots of problems with the zram virtual ram and sometimes the suspend to ram had problems and often failed, i reinstalled opensuse and created a swap partition, since i have very little ram and it is shared with the integrated gpu i made a 12 gbs swap partition, suspend to ram is doing fine here so far
about usb devices, in itself if i ever dare to touch mouse, the machine will wake up instantaneously, almost as fast as when i tell it to sleep, so y turn off mouse being wireless via usb receiver or it will wake up by itself so easily, btw my pc has two logitech receivers, one is unifying, the other is a just for the mouse receiver, none gives problems so far
would be useful if is a logitech wireless peripheral receiver to check if there are firmware updates for it, but iirc the site asks for a windows machine to run the update tool, but this is only important if the op also has a logitech device
@nameles27 have you never run fwupdmgr get-updates?
fwupdmgr get-updates
• Windows Production PCA
• KEK CA
• Key Exchange Key
• Option ROM UEFI CA
• SBAT
• SPCC M.2 PCIe SSD
• SPCC Solid State Disk
• TPM
• UEFI DB
Devices with the latest available firmware version:
• System Firmware
• UEFI CA
• UEFI dbx
• Unifying Receiver <<========
No updates available
i didnt knew such tool existed, thank you for sharing that
WARNING: UEFI firmware can not be updated in legacy BIOS mode
See https://github.com/fwupd/fwupd/wiki/PluginFlag:legacy-bios for more information.
Devices with no available firmware updates:
• GIGABYTE GP-GSM2NE8256GNTD
• KINGSTON SA400S37120G
Devices with the latest available firmware version:
• Unifying Receiver
No updates available
lol, in my bios it says clearly uefi only, well, such is life, still worth to have such solution for those who can use it
returns nothing.
Here is a new log without filters:
nov 05 16:26:00 systemd-logind[975]: suspend requested from client PID 1897 ('org_kde_powerde') (unit user@1000.service)...
nov 05 16:26:00 systemd-logind[975]: The system will suspend now!
nov 05 16:26:00 org_kde_powerdevil[1897]: Watching for display connection changes, resolved watch mode = Watch_Mode_Udev, poll loop interval = 500 millisec
nov 05 16:26:00 org_kde_powerdevil[1897]: initial_stabilization_millisec: 0, stabilization_poll_millisec: 100
nov 05 16:26:00 org_kde_powerdevil[1897]: [ 1932][292.661865] (ldbus_handle_message)Received dbus signal PrepareForSleep(true=prepare)
nov 05 16:26:00 NetworkManager[1189]: <info> [1793892360.6076] manager: sleep: sleep requested (sleeping: no enabled: yes)
nov 05 16:26:00 google-chrome-stable[2141]: [2116:2389:1105/162600.614747:ERROR:google_apis/gcm/engine/connection_factory_impl.cc:474] ConnectionHandler failed with net error: -2
nov 05 16:26:00 rtkit-daemon[1656]: Demoting known real-time threads.
nov 05 16:26:00 NetworkManager[1189]: <info> [1793892360.6103] device (wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
nov 05 16:26:00 ModemManager[1082]: <msg> [sleep-monitor-systemd] system is about to suspend
nov 05 16:26:00 NetworkManager[1189]: <info> [1793892360.6111] device (wlo1): set-hw-addr: reset MAC address to XX:XX:XX:18:C2:B1 (unmanage)
nov 05 16:26:00 ModemManager[1082]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
nov 05 16:26:00 NetworkManager[1189]: <info> [1793892360.6124] manager: NetworkManager state is now DISABLED (ASLEEP)
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 6012 of process 4598.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 5820 of process 2080.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 5546 of process 2080.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 3827 of process 2076.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 2939 of process 2152.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1708 of process 1705.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1705 of process 1705.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1652 of process 1643.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1643 of process 1643.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1662 of process 1644.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1657 of process 1644.
nov 05 16:26:00 rtkit-daemon[1656]: Successfully demoted thread 1644 of process 1644.
nov 05 16:26:00 rtkit-daemon[1656]: Demoted 12 threads.
nov 05 16:26:00 systemd[1]: Starting PackageKit Daemon...
nov 05 16:26:00 PackageKit[7809]: daemon start
nov 05 16:26:00 systemd-logind[975]: Suspend key pressed short.
nov 05 16:26:00 systemd[1]: Started PackageKit Daemon.
nov 05 16:26:00 systemd[1]: Reached target Sleep.
nov 05 16:26:00 systemd[1]: Starting System Suspend...
nov 05 16:26:00 systemd[1]: session-3.scope: Unit now frozen-by-parent.
nov 05 16:26:00 systemd[1]: user.slice: Unit now frozen.
nov 05 16:26:00 systemd[1]: user-1000.slice: Unit now frozen-by-parent.
nov 05 16:26:00 systemd[1]: user@1000.service: Unit now frozen-by-parent.
nov 05 16:26:00 systemd-sleep[7823]: Successfully froze unit 'user.slice'.
nov 05 16:26:00 systemd-sleep[7823]: Performing sleep operation 'suspend'...
nov 05 16:26:00 kernel: PM: suspend entry (deep)
-- Boot 5ed714f7442b47e4b3e5a0b9e4b5f924 --
nov 05 17:26:40 kernel: Linux version 7.3.1-1-default (geeko@buildhost) (gcc (SUSE Linux) 16.2.1 20260929, GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.47.0.20260921-2) #1 SMP PREEMPT_DYNAMIC Sat Oct 31 11:17:21 UTC 2026 (8815021)
nov 05 17:26:40 kernel: Command line: initrd=\opensuse-tumbleweed\7.3.1-1-default\initrd-805b1065c7f5ded9f415d52d38c80f67274279a6 root=UUID=998ab041-ba89-425b-b497-ce75af0b0458 splash=silent quiet security=selinux selinux=1 mem_sleep_default=deep mitigations=auto rootflags=subvol=@/.snapshots/1/snapshot
nov 05 17:26:40 kernel: x86/CPU: Model not found in latest microcode list
nov 05 17:26:40 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
nov 05 17:26:40 kernel: BIOS-provided physical RAM map:
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] System RAM
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000053acafff] System RAM
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000053acb000-0x0000000064a3bfff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000064a3c000-0x0000000064bc6fff] ACPI NVS
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000064bc7000-0x0000000064c95fff] ACPI data
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000064c96000-0x00000000671b8fff] System RAM
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000671b9000-0x00000000671b9fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000671ba000-0x00000000672c6fff] System RAM
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000672c7000-0x00000000672cafff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000672cb000-0x00000000672ccfff] ACPI NVS
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000672cd000-0x000000006fffffff] System RAM
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000070000000-0x00000000807fffff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x0000000080800000-0x00000000dfffffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000f0000000-0x00000000fdffffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fe011000-0x00000000fe7fffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fe800000-0x00000000fe800fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fe801000-0x00000000febfffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fec01000-0x00000000fecfffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fed01000-0x00000000fed1ffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed8ffff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fed90000-0x00000000fedfffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [gap 0x00000000fee01000-0x00000000feffffff]
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000001083fffff] device reserved
nov 05 17:26:40 kernel: BIOS-e820: [mem 0x0000000108400000-0x000000107f7fffff] System RAM
nov 05 17:26:40 kernel: NX (Execute Disable) protection: active
nov 05 17:26:40 kernel: APIC: Static calls initialized
nov 05 17:26:40 kernel: efi: EFI v2.10 by American Megatrends
nov 05 17:26:40 kernel: efi: ACPI=0x64b3e000 ACPI 2.0=0x64b3e014 TPMFinalLog=0x64aaa000 SMBIOS=0x593a8000 SMBIOS 3.0=0x593a7000 MEMATTR=0x4d3dc018 ESRT=0x50d5d698 MOKvar=0x55a41000 RNG=0x64bf0f18 INITRD=0x4cd6cb18 TPMEventLog=0x64be6018
nov 05 17:26:40 kernel: random: crng init done
nov 05 17:26:40 kernel: efi: Remove mem343: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
nov 05 17:26:40 kernel: e820: remove [mem 0xe0000000-0xefffffff] device reserved
nov 05 17:26:40 kernel: efi: Not removing mem344: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
nov 05 17:26:40 kernel: efi: Not removing mem345: MMIO range=[0xfe800000-0xfe800fff] (4KB) from e820 map
nov 05 17:26:40 kernel: efi: Not removing mem346: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
nov 05 17:26:40 kernel: efi: Not removing mem347: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
nov 05 17:26:40 kernel: efi: Not removing mem349: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
nov 05 17:26:40 kernel: efi: Remove mem350: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
nov 05 17:26:40 kernel: e820: remove [mem 0xff000000-0xffffffff] device reserved
nov 05 17:26:40 kernel: secureboot: Secure boot disabled
nov 05 17:26:40 kernel: DMI: SMBIOS 3.8.0 present.
nov 05 17:26:40 kernel: DMI: ASUS NUC16GDKU76/NUC16GDBU76, BIOS GDPTL579.0043.2026.1006.2022 10/06/2026
nov 05 17:26:40 kernel: DMI: Memory slots populated: 2/2
nov 05 17:26:40 kernel: tsc: Detected 3700.000 MHz processor
nov 05 17:26:40 kernel: tsc: Detected 3686.400 MHz TSC
nov 05 17:26:40 kernel: e820: update [mem 0x00000000-0x00000fff] System RAM ==> device reserved
nov 05 17:26:40 kernel: e820: remove [mem 0x000a0000-0x000fffff] System RAM
nov 05 17:26:40 kernel: last_pfn = 0x107f800 max_arch_pfn = 0x400000000
nov 05 17:26:40 kernel: MTRR map: 9 entries (3 fixed + 6 variable; max 23), built from 10 variable MTRRs
nov 05 17:26:40 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
nov 05 17:26:40 kernel: x2apic: enabled by BIOS, switching to x2apic ops
nov 05 17:26:40 kernel: last_pfn = 0x70000 max_arch_pfn = 0x400000000
nov 05 17:26:40 kernel: esrt: Reserving ESRT space from 0x0000000050d5d698 to 0x0000000050d5d838.
nov 05 17:26:40 kernel: e820: update [mem 0x50d5d000-0x50d5dfff] System RAM ==> device reserved
nov 05 17:26:40 kernel: Using GB pages for direct mapping
nov 05 17:26:40 kernel: secureboot: Secure boot disabled
nov 05 17:26:40 kernel: RAMDISK: [mem 0x44404000-0x4756ffff]
I have nothing wireless. There is only a single usb cable to my monitor that serves as a usb hub, it has usb mouse and keyboard connected. These same mouse and keyboard worked fine with another PC and they were connected the same way.
fwupdmgr get-updates
Devices with no available firmware updates:
• ASUS KEK Certificate
• ASUS UEFI SW Key Certificate
• Internal SPI Controller (BIOS)
• Hub
• KEK CA
• Option ROM UEFI CA
• PCH SPI Controller
• SSD 990 PRO 2TB
• System Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
Devices with the latest available firmware version:
• UEFI CA
• UEFI dbx
• Windows UEFI CA
No updates available
The log shows that the machine reboots as soon as it tries to enter S3 suspend, which suggests that the motherboard does not support Suspend-to-RAM. I think rather than trying to get S3 working, you should try to figure out what is interrupting s2idle.
Your USB devices may not be causing any problems on another PC, but that PC is likely using S3 suspend which is much less susceptible to hardware conflicts.
Try switching back to s2idle and getting logs from suspend there to see what is going on there.
I don’t think it’s a fix, but there appears to have been a BIOS update released for your machine last month. Is it applied?