Bug 217067 - pcie_aspm policy dependent high power consumption during s2idle in ThinkPad T14s
Summary: pcie_aspm policy dependent high power consumption during s2idle in ThinkPad T14s
Status: NEW
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Rafael J. Wysocki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-21 20:52 UTC by Lev Melnikovsky
Modified: 2023-02-21 20:58 UTC (History)
1 user (show)

See Also:
Kernel Version: 6.1.11-arch1-1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
powersupersave S0ixSelftestTool log (1.83 KB, text/plain)
2023-02-21 20:54 UTC, Lev Melnikovsky
Details
powersave S0ixSelftestTool log (7.16 KB, text/plain)
2023-02-21 20:55 UTC, Lev Melnikovsky
Details
default S0ixSelftestTool log (1.83 KB, text/plain)
2023-02-21 20:55 UTC, Lev Melnikovsky
Details
performance S0ixSelftestTool log (7.14 KB, text/plain)
2023-02-21 20:57 UTC, Lev Melnikovsky
Details

Description Lev Melnikovsky 2023-02-21 20:52:43 UTC
Hi, I'm running arch on a new ThinkPad T14s (3Gen Intel). Old school S3 suspend is unusable (kernel panic on resume).

In S2idle the battery drain is inconsistent, raniging from 10% to 50% overnight. Seems to be related to the contents of /sys/module/pcie_aspm/parameters/policy (tweaked by laptop-mode-tools) prior to suspend. Particularly, the policies "default" and "powersupersave" correspond to low battery drain, while "performance" and "powersave" prevent PC8 during suspend. Below is an excerpt from S0ixSelftestTool output, full logs for all policies are attached.

----------------------------------------------------------------------------
Available bridge device: 0000:00:06.0 0000:00:07.0 0000:00:07.2

The PCIe bridge link power management state is:
0000:00:06.0 Link is in L1

The link power management state of PCIe bridge: 0000:00:06.0 is not expected. 
which is expected to be L1.1 or L1.2, or user would run this script again.

The L1SubCap of the failed 0000:00:06.0 is:
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+

The L1SubCtl1 of the failed 0000:00:06.0 is:
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-

...skipped...

Checking PCI Devices tree diagram:
-[0000:00]-+-00.0  Intel Corporation Device 4621
           +-02.0  Intel Corporation Alder Lake-P Integrated Graphics Controller
           +-04.0  Intel Corporation Alder Lake Innovation Platform Framework Processor Participant
           +-06.0-[04]----00.0  Micron/Crucial Technology P2 NVMe PCIe SSD
           +-07.0-[20-49]--
           +-07.2-[50-79]--
           +-08.0  Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator
           +-0d.0  Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller
           +-0d.2  Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0
           +-0d.3  Intel Corporation Alder Lake-P Thunderbolt 4 NHI #1
           +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller
           +-14.2  Intel Corporation Alder Lake PCH Shared SRAM
           +-14.3  Intel Corporation Alder Lake-P PCH CNVi WiFi
           +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller #0
           +-16.0  Intel Corporation Alder Lake PCH HECI Controller
           +-1f.0  Intel Corporation Alder Lake PCH eSPI Controller
           +-1f.3  Intel Corporation Alder Lake PCH-P High Definition Audio Controller
           +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller
           \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller

The pcieport 0000:00:06.0 ASPM enable status:
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+

Pcieport is not in D3cold:          
0000:00:06.0

The pcieroot port 0000:00:06.0 ASPM setting is Enabled, its D state and Link PM are not expected, please investigate or report a bug.[0m
----------------------------------------------------------------------------
Comment 1 Lev Melnikovsky 2023-02-21 20:54:46 UTC
Created attachment 303766 [details]
powersupersave S0ixSelftestTool log
Comment 2 Lev Melnikovsky 2023-02-21 20:55:24 UTC
Created attachment 303767 [details]
powersave S0ixSelftestTool log
Comment 3 Lev Melnikovsky 2023-02-21 20:55:56 UTC
Created attachment 303768 [details]
default S0ixSelftestTool log
Comment 4 Lev Melnikovsky 2023-02-21 20:57:34 UTC
Created attachment 303769 [details]
performance S0ixSelftestTool log

Note You need to log in before you can comment on or make changes to this bug.