Bug 198951 - rtsx_pci does not allow package state to go down pc3 after suspend/resume
Summary: rtsx_pci does not allow package state to go down pc3 after suspend/resume
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: MMC/SD (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_mmc-sd
Depends on:
Reported: 2018-03-01 04:00 UTC by Jacopo De Simoi
Modified: 2020-07-25 19:52 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.15.5
Regression: No
Bisected commit-id:

dmesg log (451.67 KB, text/plain)
2020-07-25 19:47 UTC, Jacopo De Simoi
lscpci -vvxxxx output (164.84 KB, text/plain)
2020-07-25 19:48 UTC, Jacopo De Simoi

Description Jacopo De Simoi 2018-03-01 04:00:47 UTC

Comment 1 Jacopo De Simoi 2018-03-01 04:09:06 UTC
I am investigating some power consumption specifics of my skylake-based laptop (Thinkpad T460s).  
It appears that without the module rtsx_pci (used for the sd card reader) the package power state never goes deeper than pc3.  As soon as I modprobe the module, power state reaches up to pc7.  

After a suspend/resume cycle the power state again does not go deeper than pc3 (no error in the logs).

At this point removing and reloading the module makes low power states available again. 

Please let me know if additional information is needed.
Comment 2 James Ettle 2020-06-25 22:18:51 UTC
Still seen in 5.6.19 -- see also 208117. Have you checked if this is related to the ASPM state (see the contents of l1_aspm for this device under sysfs).
Comment 3 Jacopo De Simoi 2020-07-25 19:47:53 UTC
Created attachment 290565 [details]
dmesg log
Comment 4 Jacopo De Simoi 2020-07-25 19:48:25 UTC
Created attachment 290567 [details]
lscpci -vvxxxx output
Comment 5 Jacopo De Simoi 2020-07-25 19:52:13 UTC
The lspci output is for a working situation, after suspending and resuming, and after reloading the module.  Please let me know which other situations I need to take snapshots of

Thanks a lot for your time in looking into this.

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