You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2025-08-09 03:48:40
- omort
- Member
- Registered: 2025-08-09
- Posts: 3
Suspend mode unable to wake from sleep
Hello all! I've tried a lot of different things to help this issue, but nothing has seemed to work. I've done so many things in so many different places that I can't keep track of everything. However, something that I know for sure is that suspending didn't work when I installed the system for the first time. When I suspend, either through `systemctl suspend`, closing the lid, or through power options, my laptop will do one of two things:
1. It will either suspend properly, but when I click the power button or another key to turn it back on, it stays on a black screen with input doing nothing, and I have to force power down.
2. It will suspend improperly, with the power LED remaining on but the screen turned off, and input still doing nothing, forcing me to power down.
I've made sure sleep is enabled in /etc/systemd/sleep.conf, that suspending is the behavior when closing the lid in /etc/systemd/logind.conf, I've made sure there aren't any conflicts with TLP or other power management systems. I use GRUB as my bootloader, and I've made sure to turn off fastboot in Windows, as well as rebooting both for good measure. Here is my neofetch output:
-` omar@archlinux
.o+` --------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Kernel: Linux 6.15.9-arch1-1
`+oooooo: Uptime: 1 min
-+oooooo+: Packages: 837 (pacman)
`/:-:++oooo+: Shell: bash 5.3.3
`/++++/+++++++: Display (HKC023D): 1920x1080 @ 60 Hz in 16" [Built-in]
`/++++++++++++++: DE: KDE Plasma 6.4.4
`/+++ooooooooooooo/` WM: KWin (Wayland)
./ooosssso++osssssso+` WM Theme: Scratchy
.oossssso-````/ossssss+` Theme: Breeze (Scratchy) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
-osssssso. :ssssssso. Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
:osssssss/ osssso+++. Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
/ossssssss/ +ssssooo/- Cursor: WhiteSur (24px)
`/ossssso+/:- -:/+osssso+- Terminal: konsole 25.4.3
`+sso+:-` `.-/+oso: CPU: AMD Ryzen 7 5825U (16) @ 4.55 GHz
`++:. `-/+/ GPU: AMD Barcelo [Integrated]
.` `/ Memory: 1.89 GiB / 30.74 GiB (6%)
Swap: 0 B / 32.00 GiB (0%)
Disk (/): 39.91 GiB / 936.84 GiB (4%) - ext4
Local IP (wlan0): 192.168.0.249/24
Battery (Li-ion Real Battery): 100% [AC Connected]
Locale: en_US.UTF-8Here is my journalctl for my last boot, after suspending and turning it off: https://pastebin.com/kJApJMJz
And here are my /etc/systemd/sleep.conf and /etc/systemd/logind.conf: https://pastebin.com/MQNJrdEQ
If there are any other log files I can provide, please let me know. Thank you all in advance!
Offline
#2 2025-08-09 20:49:37
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,176
Re: Suspend mode unable to wake from sleep
Aug 08 23:13:01 archlinux kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Aug 08 23:13:01 archlinux kwin_wayland_wrapper[1216]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Aug 08 23:13:01 archlinux kwin_wayland_wrapper[1216]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Aug 08 23:13:01 archlinux kwin_wayland_wrapper[1216]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Aug 08 23:13:01 archlinux kwin_wayland_wrapper[1216]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Aug 08 23:13:01 archlinux kwin_wayland_wrapper[1216]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Aug 08 23:13:01 archlinux kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic datahttps://bbs.archlinux.org/viewtopic.php … 8#p2221728
Do you also get this when suspending from the multi-user.target (2nd link below)?
In doubt w/ "nomodeset", https://wiki.archlinux.org/title/Kernel_parameters ?
Aug 08 23:12:21 archlinux kernel: ccp 0000:03:00.2: ccp: unable to access the device: you might be running a broken BIOS.
…
Aug 08 23:12:20 archlinux kernel: DMI: Default string Default string/Default string, BIOS AB8139-S_V00.01_005 09/20/2024Are there pending firmware/uefi/bios updates for your system?
I have to force power down.
Try to avoid that at all costs and setup and attempt the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) first (the entire REISUB dance
Online
#3 2025-08-10 03:31:12
- omort
- Member
- Registered: 2025-08-09
- Posts: 3
Re: Suspend mode unable to wake from sleep
Do you also get this when suspending from the multi-user.target (2nd link below)?
I do not get those entries in journalctl when I use multi-user.target, but I am still unable to wake from sleep. Here is the associated journal for rebooting without gui, doing systemctl suspend, then attempting to wake the computer: https://pastebin.com/5a6MfAzU.
If I add the nomodeset kernel parameter, I instead am unable to sleep at all. I still get stuck in the same state where the power LED is on but any input does nothing. Even attempting to REISUB is unsuccessful, but I know it's enabled because I can reboot when the operating system is functioning normally. Here is the journalctl for that: https://pastebin.com/Jiuxb3qh
Here are my kernel parameters from /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet sysrq_always_enabled=1 amdgpu.dcdebugmask=0x10 nomodeset"Are there pending firmware/uefi/bios updates for your system?
Not that I could see. Checked with fwupdmgr get-updates, and it found no available firmware updates for the system firmware and the UEFI device firmware. I don't believe the system is active either, because when "waking up" from suspend mode, I can't SSH into it from another desktop, and as stated before, REISUB is non-functional in that state.
After some more tinkering, I noted the line "last suspend didn't reach deepest state", and found this thread: https://bbs.archlinux.org/viewtopic.php?id=288637, leading me to https://wiki.archlinux.org/title/Ryzen# … nd_suspend, so I added processor.max_cstate=1 to my kernel parameters and suddenly suspending kind of worked. The screen went black but not off and the fan also remained on, but the screen was able to wake at the click of a button. However, after removing this option from my kernel parameters and rebooting, suspending like this persists.
Here is the associated journal entry: https://pastebin.com/SbsxBUvH
Noticing the issue with the framebuffer, I removed the nomodeset kernel parameter, and got back the same behavior from before where REISUB is unsuccessful. Here is the related journal entry: https://pastebin.com/1UF9KBpp
By the fact nomodeset is able to make the computer go into some sort of suspension, it is probably something with graphics, but the fact that suspension is weird with nomodeset on as well makes me think that it has something to do with me having a Ryzen CPU as well. For now, I've resigned to simply having the screen turn off whenever the laptop lid is shut, but this isn't the best for battery life. Having only the processor.max_cstate=1 in my kernel parameters makes suspension turn the screen fully off, but the power LED and fans remain on, so the same as closing the lid. I wouldn't be too upset if I had to just have the screen turn off, especially with the weirdness around the nomodeset parameter. It is what it is!
Offline
#4 2025-08-10 07:51:55
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,176
Re: Suspend mode unable to wake from sleep
I do not get those entries in journalctl when I use multi-user.target, but I am still unable to wake from sleep.
so amdgpu/psr is a red herring
REISUB is unsuccessful, but I know it's enabled because I can reboot when the operating system is functioning
the kernel doesn't continue, so it's unlikely to be https://bbs.archlinux.org/viewtopic.php?id=296954
I noted the line "last suspend didn't reach deepest state"
is because
I add the nomodeset kernel parameter, I instead am unable to sleep at all
https://pastebin.com/SbsxBUvH is that case as well, it has nothing do do w/ the c-state.
Couple of things
-
I've made sure to turn off fastboot in Windows
Terminology: "fast-start". "Fast boot" is a feature you'll find in the firmware/uefi/bios and it's irrelevant itr - just to be sure.
- You've NM and systemd-networkd enabled, probably disable the latter
- is deep sleep (S3) and option? "cat /sys/power/mem_sleep"
- https://wiki.archlinux.org/title/Ryzen#System_halts (since limiting the c-states was unsuccessful, you'd be looking at the PBO curve optimizer)
- https://wiki.archlinux.org/title/Solid_ … leshooting - while that should™ still allow you to sysrq+reisub, try adding "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft" and as a hail mary (if those have no effect) also "pcie_port_pm=off" (make sure to be able to edit this at the grub commandline editor, the system might fail to boot w/ this)
Online
#5 2025-08-10 16:26:35
- omort
- Member
- Registered: 2025-08-09
- Posts: 3
Re: Suspend mode unable to wake from sleep
- is deep sleep (S3) and option? "cat /sys/power/mem_sleep"
Output was "[s2idle]".
the kernel doesn't continue, so it's unlikely to be https://bbs.archlinux.org/viewtopic.php?id=296954
Added the config files from here as well, just to see what would happen.
- https://wiki.archlinux.org/title/Solid_ … leshooting - while that should™ still allow you to sysrq+reisub, try adding "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft" and as a hail mary (if those have no effect) also "pcie_port_pm=off" (make sure to be able to edit this at the grub commandline editor, the system might fail to boot w/ this)
Added all to kernel parameters and no results. Rebooted the system and added "pcie_port_pm=off" to the arguments at startup, no dice. I'm still unable to REISUB when the laptop "wakes up" from suspending. Here's the journal entry for the last run, with all the kernel parameters and "pcie_port_pm=off": https://pastebin.com/gpzEVuL6
I believe the problem starts when the system tries to wake up from suspend at C3. Incrementing processor.max_cstate in my kernel parameters from 1, to 2, then 3, processor.max_cstate=3 exhibited the behavior of suspending properly, then being unable to wake up, and REISUB not working. processor.max_cstate=1 and 2 result in the behavior of the screen turning off, but the power LED and fans remaining on. This behavior happens with the nvme_core, pcie_aspm, and iommu kernel parameters.
I think the wiki article about troubleshooting drives is on the right track for what my issue might be, this is the output of smartctl -c /dev/nvme0
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.50W - - 0 0 0 0 0 0
1 + 5.80W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.7460W - - 3 3 3 3 5000 10000
4 - 0.7260W - - 4 4 4 4 8000 45000C3 is when the drive first has any latency for entering and exiting, so perhaps something to do with that? If I set processor.max_cstate=3, even with nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, it is unable to wake up, meaning that it's still going into a deeper sleep despite the kernel parameters. The processor.max_cstate parameter is definitely working, using amdctl from the AUR, the P-state limits are what they should be for my current parameters, with the highest being 0 and the lowest being 2.
Offline
#6 2025-08-10 19:06:32
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,176
Re: Suspend mode unable to wake from sleep
processor.max_cstate=1 and 2 result in the behavior of the screen turning off, but the power LED and fans remaining on.
That's WITHOUT nomodeset?
Do you have a journal for that attempt?
There was https://wiki.archlinux.org/title/Intel_ … up_from_S3 …
Online
Pages: 1