Lenovo 13w AMD - High Power Draw during Suspend

[spynoodle]

Hi all,

I’m new to Manjaro, and so far have been loving it after installing it on my Lenovo 13w laptop a few weeks ago. The only major issue I have is that I am experiencing abnormally high battery drain when the laptop is asleep; with Windows 11 I could leave the laptop suspended for days with minimal battery drain, but with Manjaro I lose ~30% a day. I ran the amd-s2idle diagnostic script that I found scattered in some other Arch forums to try and help diagnose my problem, but I’m at a loss for what to do next. The full diagnostic output is pasted below. It seems like the following lines referring to issues with my audio coprocessor and SSD may be the culprit, but I’m not sure what could be wrong with these devices:

PM: noirq suspend of devices complete after 80.297 msecs
ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
ACPI: \_SB_.PCI0.GP18.SATA: LPI: Constraint not met; min power state:D3hot current power state:D0
ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Constraint not met; min power state:D3hot current power state:D0

Does anyone have any ideas? Thanks in advance!

# Linux s2idle Power Report

s2idle report created 2026-01-10 10:57:57.723456 using amd-s2idle 0.2.11

|💻|AMD Ryzen 5 5625U with Radeon Graphics (family 19 model 50)|
| --- | --- |
|💻|LENOVO 82S1 (13w Yoga)|
|🐧|Manjaro Linux|
|🐧|Kernel 6.12.63-1-MANJARO|
|🔋|Battery BAT0 (SMP LNV-5B11F53996) is operating at 92.43% of design|
|✅|ASPM policy set to 'default'|
|✅|GPIO driver `pinctrl_amd` available|
|✅|PMC driver `amd_pmc` loaded (Program 0 Firmware 64.74.0)|
|✅|USB3 driver `xhci_hcd` bound to 0000:05:00.3, 0000:05:00.4|
|✅|System is configured for s2idle|
|✅|GPU driver `amdgpu` bound to 0000:05:00.0|
|🚦|Unable to discover CPU topology, didn't find socket level|
|✅|PC6 and CC6 enabled|
|✅|SMT enabled|
|✅|ACPI FADT supports Low-power S0 idle|
|✅|Logs are provided via cysystemd|
|✅|LPS0 _DSM enabled|
|✅|WLAN driver `rtw89_8852be` bound to 0000:03:00.0|

### Prerequisites
DMI	value
bios_date	03/10/2025
bios_release	1.44
bios_vendor	LENOVO
bios_version	JACN44WW
board_name	LNVNB161216
board_vendor	LENOVO
board_version	SDK0T76530 WIN
chassis_type	31
chassis_vendor	LENOVO
chassis_version	Lenovo 13w Yoga
ec_firmware_release	1.30
product_sku	LENOVO_MT_82S1_BU_idea_FM_13w Yoga
product_version	Lenovo 13w Yoga
VCE feature version: 0, firmware version: 0x00000000
UVD feature version: 0, firmware version: 0x00000000
MC feature version: 0, firmware version: 0x00000000
ME feature version: 54, firmware version: 0x000000a7
PFP feature version: 54, firmware version: 0x000000c4
CE feature version: 54, firmware version: 0x00000050
RLC feature version: 1, firmware version: 0x0000003c
RLC SRLC feature version: 1, firmware version: 0x00000001
RLC SRLG feature version: 1, firmware version: 0x00000001
RLC SRLS feature version: 1, firmware version: 0x00000001
RLCP feature version: 0, firmware version: 0x00000000
RLCV feature version: 0, firmware version: 0x00000000
MEC feature version: 54, firmware version: 0x000001e1
IMU feature version: 0, firmware version: 0x00000000
SOS feature version: 0, firmware version: 0x00000000
ASD feature version: 0, firmware version: 0x21000104
TA XGMI feature version: 0x00000000, firmware version: 0x00000000
TA RAS feature version: 0x00000000, firmware version: 0x00000000
TA HDCP feature version: 0x00000000, firmware version: 0x1700004a
TA DTM feature version: 0x00000000, firmware version: 0x1200001a
TA RAP feature version: 0x00000000, firmware version: 0x00000000
TA SECUREDISPLAY feature version: 0x00000000, firmware version: 0x00000000
SMC feature version: 0, program: 0, firmware version: 0x00404a00 (64.74.0)
SDMA0 feature version: 41, firmware version: 0x00000028
VCN feature version: 0, firmware version: 0x08118009
DMCU feature version: 0, firmware version: 0x00000000
DMCUB feature version: 0, firmware version: 0x0101002b
TOC feature version: 0, firmware version: 0x00000000
MES_KIQ feature version: 0, firmware version: 0x00000000
MES feature version: 0, firmware version: 0x00000000
VPE feature version: 0, firmware version: 0x00000000
VBIOS version: 113-BARCELO-004
LOGIND: no configuration changes

## Summary

||Start Time|Duration|Hardware Sleep|Battery Start|Battery Delta|Battery Ave Rate|Wake Pin|Wake Interrupt|
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|0|2026-01-10 10:54:44|0:03:13|92.23%|42.54%|-0.17%|-1.15W|44|ACPI SCI, PS/2 controller, GPIO Controller|

💤 Hardware sleep cycle count: 1

💤 Notify devices ['DEV0', 'AMW1', 'UBTC'] found during suspend


### Debugging 🦟


BAT0 energy level is 20060000 µWh
ACPI Lid (/proc/acpi/button/lid/LID0/state): open

/proc/cmdline:

Wakeup Source Linux Device Status
ACPI Battery PNP0C0A:00 enabled
ACPI Lid Switch PNP0C0D:00 enabled
ACPI Power Button PNP0C0C:00 enabled
AT Translated Set 2 keyboard serio0 enabled
Advanced Micro Devices, Inc. [AMD] ISA bridge 0000:00:14.3 enabled
Advanced Micro Devices, Inc. [AMD] PCI bridge 0000:00:01.2 enabled
Advanced Micro Devices, Inc. [AMD] PCI bridge 0000:00:08.1 enabled
Advanced Micro Devices, Inc. [AMD] USB controller 0000:05:00.3 enabled
Advanced Micro Devices, Inc. [AMD] USB controller 0000:05:00.4 enabled
ELAN0644:00 04F3:31B2 Mouse i2c-ELAN0644:00 enabled
Plug-n-play Real Time Clock 00:01 enabled
Real Time Clock alarm timer rtc0 enabled
Wacom HID 52FF Pen i2c-WACF2200:00 enabled
/sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001/wakeup61 enabled
/sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002/wakeup58 enabled
kwin_wayland compositor is running
Power Profiles:
│ performance:
│ CpuDriver: amd_pstate
└─PlatformDriver: platform_profile
│ Degraded: no
│ * balanced:
│ CpuDriver: amd_pstate
└─PlatformDriver: platform_profile
│ power-saver:
│ CpuDriver: amd_pstate
└─PlatformDriver: platform_profile
Thermal zones
├─ LNXTHERM:00
│ temp: 33.0°C
│ critical trip: 118.0°C
└─LNXTHERM:01
temp: 25.0°C
critical trip: 126.0°C
Suspend timer programmed for 0:03:00
PM: suspend entry (s2idle)
Filesystems sync: 0.112 seconds
Freezing user space processes
Freezing user space processes completed (elapsed 0.002 seconds)
OOM killer disabled.
Freezing remaining freezable tasks
Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
printk: Suspending console(s) (use no_console_suspend to debug)
wlp3s0: deauthenticating from 58:9b:4a:90:76:0c by local choice (Reason: 3=DEAUTH_LEAVING)
PM: suspend of devices complete after 230.083 msecs
PM: start suspend of devices complete after 260.011 msecs
Clearing debounce for GPIO #0 during suspend.
Disabling GPIO #9 interrupt for suspend.
Disabling GPIO #17 interrupt for suspend.
PM: late suspend of devices complete after 0.947 msecs
ACPI: EC: interrupt blocked
PM: noirq suspend of devices complete after 80.297 msecs
ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
ACPI: \_SB_.PCI0.GP18.SATA: LPI: Constraint not met; min power state:D3hot current power state:D0
ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Constraint not met; min power state:D3hot current power state:D0
PM: Triggering wakeup from IRQ 9
ACPI: \_SB_.PEP_: Successfully transitioned to state screen off
ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms entry
ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 entry
amd_pmc: wakeup timer programmed for 179 seconds
PM: suspend-to-idle
ACPI: EC: ACPI EC GPE status set
ACPI: PM: Rearming ACPI SCI for wakeup
amd_pmc: SMU idlemask s0i3: 0xc02f0eb5
Timekeeping suspended for 179.047 seconds
PM: Triggering wakeup from IRQ 1
PM: Triggering wakeup from IRQ 7
ACPI: PM: Wakeup unrelated to ACPI SCI
PM: resume from suspend-to-idle
ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 exit
PM: Triggering wakeup from IRQ 0
Dispatching Notify on [DEV0] (Device) Value 0x01 (Device Check)
ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms exit
ACPI: \_SB_.PEP_: Successfully transitioned to state screen on
ACPI: EC: interrupt unblocked
PM: noirq resume of devices complete after 10392.419 msecs
GPIO 44 is active: 0x30007800
PM: Triggering wakeup from IRQ 0
Dispatching Notify on [AMW1] (Device) Value 0xB0 (Device-Specific)
PM: early resume of devices complete after 0.824 msecs
[drm] PCIE GART of 1024M enabled.
[drm] PTB located at 0x000000F41FC00000
amdgpu 0000:05:00.0: amdgpu: SMU is resuming...
amdgpu 0000:05:00.0: amdgpu: dpm has been disabled
amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully!
nvme nvme0: 12/0/0 default/read/poll queues
nvme nvme0: resetting controller due to persistent internal error
nvme nvme1: 12/0/0 default/read/poll queues
nvme nvme0: Identify namespace failed (-4)
Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change)
Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change)
nvme nvme0: 12/0/0 default/read/poll queues
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
PM: resume of devices complete after 429.028 msecs
OOM killer enabled.
Restarting tasks ...
usb 3-3: USB disconnect, device number 6
Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
done.
random: crng reseeded on system resumption
Bluetooth: hci0: RTL: rom_version status=0 version=1
Bluetooth: hci0: RTL: btrtl_initialize: key id 0
Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
PM: suspend exit
Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
Bluetooth: hci0: RTL: cfg_sz 6, total sz 60107
usb 3-3: new full-speed USB device number 7 using xhci_hcd
usb 3-3: New USB device found, idVendor=06cb, idProduct=00f9, bcdDevice= 0.00
usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1
usb 3-3: SerialNumber: aaffe919f382
Bluetooth: hci0: RTL: fw version 0x42d34e04
wlp3s0: authenticate with 58:9b:4a:90:76:0b (local address=e0:0a:f6:76:ae:17)
wlp3s0: send auth to 58:9b:4a:90:76:0b (try 1/3)
wlp3s0: authenticated
wlp3s0: associate with 58:9b:4a:90:76:0b (try 1/3)
wlp3s0: RX AssocResp from 58:9b:4a:90:76:0b (capab=0x1011 status=0 aid=17)
Bluetooth: hci0: AOSP extensions version v1.00
Bluetooth: MGMT ver 1.23
wlp3s0: associated
wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 58:9b:4a:90:76:0b
Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Used Microsoft uPEP GUID in LPS0 _DSM
Woke up from IRQ 1 (IR-IO-APIC 1-edge i8042)
gpe03 increased from 708 to 751
ACPI Lid (/proc/acpi/button/lid/LID0/state): open
BAT0 energy level is 19980000 µWh
Thermal zones
├─ LNXTHERM:00
│ 33.0°C -> 31.0°C
└─LNXTHERM:01
25.0°C -> 26.0°C

[soundofthunder]

@spynoodle – Welcome to the Manjaro community

The Manjaro forum has minimum requirements for presentation, including that any code or command output should be placed within a scrollable pre-formatted text enclosure according to forum guidelines.

Please edit your post accordingly.

This has been partially done for you, this one time only; in future you are expected to attend to this yourself.

Regards.

---

[MiniHowTo] Present code or command output

Code or command output is expected to be presented similarly to how it would appear in a text editor (monospaced). The Discourse forum software makes it easy to create an enclosure (a text box) that is already pre-formatted for this purpose.

Note: Grave accent (or, backtick) characters are used.

For inline code or to show a single command:

• please follow this simple example: code here.

For multi-line command output:

• place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
• use the </> button in the Compose window to achieve the same result.

Important: Click the </> button and paste text between the backticks (if using the old Compose layout). Otherwise, paste into the box generated (if using the new Compose layout).

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.

---

[spynoodle]

Hi,

I think I have fixed it now. Could you please relist the post? Thanks!

[soundofthunder]

@spynoodle

@spynoodle

I think I have fixed it now

Done. I only unlisted it while I was making edits to your post – that took longer than expected and I forgot to relist it straight away.

Regards.

[spynoodle]

For anyone who finds this thread at some point: I determined that my power draw under s2idle is likely somewhat normal, and I may have just been psyching myself out. After running the amd-s2idle diagnostic for a longer period (30 minutes), the report indicated a hardware sleep percentage of ~99% and an average power draw of 0.75W, which is apparently not abnormal. I think that part of my confusion stemmed from the fact that Windows automatically enters hibernate during long sleep periods in order to save power.

On a related note, my Manjaro install also refused to hibernate - it would simply hang at a powered-on black screen and never fully shut down. I eventually figured out that this was just a weird power state issue, and solved that problem by adding HibernateMode=shutdown to my /etc/systemd/sleep.conf file. Hope this helps someone who sees this in the future!