# Suspend doesn't reach deepest state, battery usage high **URL:** \ **Category:** Linux\ **Tags:** arch\ **Created:** [March 8, 2025, 2:49pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786 "2025-03-08T14:49:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Reed\_Law](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reed_law/32/34952_2.png) [@Reed\_Law](https://community.frame.work/u/Reed_Law)\ **Post date:** [March 8, 2025, 2:49pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/1 "2025-03-08T14:49:54Z")
Which Linux distro are you using? Arch Which release version? Updated today Which kernel are you using? 6.13.5-arch1-1 Which BIOS version are you using? 03.05 Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series) AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Hi, Lately suspend hasn’t been working properly. Overnight the battery runs very low or completely out. When I open the laptop, it resumes very quickly as if it wasn’t suspended. Look at the logs with `journalctl -b | grep -i suspend` I see: ```auto kernel: amd_pmc AMDI0009:00: Last suspend didn't reach deepest state ``` In `/sys/power/mem_sleep`: ```auto [s2idle] ``` `uptime -s` shows the last time I rebooted, not the last time it resumed from suspend. The kernel message is suspicious but I’m not sure what to do about it. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [March 8, 2025, 3:26pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/2 "2025-03-08T15:26:57Z")
Triage with [amd\_s2idle.py - kernel/git/superm1/amd-debug-tools.git - Debug tools for AMD zen systems](https://web.git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/tree/amd_s2idle.py) Post the report to gist if you don’t have conclusions from script. If it’s a kernel regression please bisect. ---
**Author:** ![Reed\_Law](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reed_law/32/34952_2.png) [@Reed\_Law](https://community.frame.work/u/Reed_Law)\ **Post date:** [March 8, 2025, 3:40pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/3 "2025-03-08T15:40:25Z")
It says I have a tainted kernel due to virtualbox-host-modules-arch. Uninstalled and will see if the problem persists. After reboot I ran the script. [Results](https://gist.github.com/reedlaw/546556ce67b78e99259e013e9471bf94) This part is worrisome: ```auto 2025-03-08 10:44:42,819 INFO: 🔋 Battery BAT1 lost 3000 µAh (0.06%) [Average rate: 1.06A] ``` ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [March 21, 2025, 4:20pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/4 "2025-03-21T16:20:36Z")
[edit] ```auto 2025-03-08 10:44:42,814 DEBUG: evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 0000000055a561af 2025-03-08 10:44:42,814 DEBUG: evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 0000000055a561af 2025-03-08 10:44:42,814 DEBUG: evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 0000000055a561af 2025-03-08 10:44:42,814 DEBUG: evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 0000000055a561af ``` Try suspending with nothing plugged into the ports. See if that helps you. ---
**Author:** ![Reed\_Law](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reed_law/32/34952_2.png) [@Reed\_Law](https://community.frame.work/u/Reed_Law)\ **Post date:** [March 21, 2025, 6:23pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/5 "2025-03-21T18:23:51Z")
Same result (Average rate: 1.1A). I see only two `evmisc-0132 ev_queue_notify_reques` lines now. What do they mean? ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [March 21, 2025, 6:58pm UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/6 "2025-03-21T18:58:57Z")
I’ll need to see what they’re notifying to tell you what they mean. Make sure you run a long enough cycle - some of the hardware needs enough time to settle. ---
**Author:** ![Reed\_Law](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reed_law/32/34952_2.png) [@Reed\_Law](https://community.frame.work/u/Reed_Law)\ **Post date:** [March 22, 2025, 11:58am UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/7 "2025-03-22T11:58:22Z")
I gave it 30 seconds with two runs. The second time did not reach hardware sleep state. [Results](https://gist.github.com/reedlaw/8334b5c6c9f7fbc914085cde57061017) ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [March 31, 2025, 4:24am UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/8 "2025-03-31T04:24:14Z")
Where is the report that failed to get hardware sleep state? The one you shared seems to have reached it. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\ **Post date:** [September 27, 2025, 4:24am UTC](https://community.frame.work/t/suspend-doesnt-reach-deepest-state-battery-usage-high/65786/9 "2025-09-27T04:24:15Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.