Bug 219284 - sdhci_pci module is blocking low power s0ix sleep with GL9767
Summary: sdhci_pci module is blocking low power s0ix sleep with GL9767
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: MMC/SD (show other bugs)
Hardware: Intel Linux
: P3 normal
Assignee: drivers_mmc-sd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-16 14:54 UTC by Georg Gottleuber
Modified: 2024-12-16 21:23 UTC (History)
2 users (show)

See Also:
Kernel Version: 6.11
Subsystem:
Regression: No
Bisected commit-id:


Attachments
kernel.log s2idle without and with sdhci_pci module (150.48 KB, text/plain)
2024-09-16 14:54 UTC, Georg Gottleuber
Details

Description Georg Gottleuber 2024-09-16 14:54:38 UTC
Created attachment 306887 [details]
kernel.log s2idle without and with sdhci_pci module

S2idle sleep on TUXEDO InfinityBook Pro 14 Gen9 Intel laptop with GL9767 SD card reader consumes 6 watts. Intel Core Ultra 7 155H is not entering s0ix properly. If I blacklist sdhci_pci in /etc/modprobe.d/blacklist.conf then the device sleeps with 1.2 watts (this is not super good, but OK). Unfortunately unloading and reloading does not work either. Once the module has been loaded, the high power consumption remains, even after a rmmod.

I tested this behavior with linux mainline 6.11.0-rc7, 6.11.0-rc7-next-20240909. Kernel mmc/next does not work either.

I also used Intel S0ix Selftest Tool and it blamed the GL9767 SD card reader.
Comment 1 Georg Gottleuber 2024-09-23 12:11:37 UTC
I was able to reproduce the behaviour with kernel v6.11.
Comment 2 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-09-25 13:37:29 UTC
In case this is a regression (sounds like it's not!) please let me know.

Side note: reminder, there is a decent chance that your report here won't be seen by the developers; for details search for "bugzilla" in documents like https://docs.kernel.org/admin-guide/reporting-issues.html or https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
Comment 3 Georg Gottleuber 2024-09-30 12:51:11 UTC
In an AMD device (InfinityBook Pro 14 Gen9 AMD), however, the same card 
reader sleeps without any problems.
Comment 4 GRbit 2024-12-16 20:01:07 UTC
I have InfinityBook Pro 14 Gen9 AMD and have troubles with going to sleep and back.

After debugging suspend using this instruction https://www.kernel.org/doc/html/latest/power/s2ram.html I found this logs in dmesg:

[    0.638016] PM:   Magic number: 0:66:178
[    0.638019] PM:   hash matches drivers/base/power/main.c:1272
[    0.638074] acpi PNP0C02:0b: hash matches
[    0.638093] acpi device:0e: hash matches

device:0e points to 
00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix GPP Bridge
04:00.0 SD Host controller: Genesys Logic, Inc GL9767 SD Host Controller (rev 03)

I have no idea which information could be helpful, but I'm willing to provide any needed info.
Comment 5 GRbit 2024-12-16 20:04:47 UTC
I'm sorry, I didn't provide the exact description of "troubles" I mentioned. For me, after going to sleep, I can not resume. The laptop just boots starting from grub menu.
Comment 6 GRbit 2024-12-16 21:23:10 UTC
Well, I must admit I'm not used to think before I write. Modern platforms that allow to edit your messages made me lazy.

Some more info on the topic:

I've tested suspend on tuxedo kernel:
$ uname -a
Linux tuxedo-inf9 6.11.0-107011-tuxedo #11tuxnoble1 SMP PREEMPT_DYNAMIC Sat Nov  9 11:02:15 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

After that I found a public thread with a patch to the problem of the topic starter: https://www.spinics.net/lists/linux-mmc/msg82920.html

I'm not sure how to check the code of the 6.11.0-107011-tuxedo kernel, yet I found that this patch is applied on the latest kernel version 6.12.5
I copied configs of the tuxedo kernel and build a 6.12.5 kernel with "make -j bindeb-pkg"

Unfortunately, s2ram still gives me the same problem: system can not go to sleep properly and just turns off. Blacklisting sdhci module didn't help, I still see the same messages in dmesg.

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