Bug 205871
| Summary: | Issues with GL9750 after reboot from Windows 10. Ok with clean boot. | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Grzegorz Kowal (custos.mentis) |
| Component: | MMC/SD | Assignee: | drivers_mmc-sd |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | custos.mentis, postix, victording |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.4.3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg after reboot from Windows 10
dmesg after clean boot top output lspci after reboot from Windows 10 lspci after clean boot Fix for the restart from Windows 10 issue |
||
Created attachment 286309 [details]
dmesg after clean boot
Created attachment 286311 [details]
top output
Created attachment 286313 [details]
lspci after reboot from Windows 10
Created attachment 286315 [details]
lspci after clean boot
Added lspci -s 05:00.0 -vvvv after reboot from Windows 10 and after clean boot to Linux.
I've contacted Ben Chuang, the author of Genesys Logic GL975x, and after some investigation he provided a patch to solve the problem. I am attaching this patch. Hopefully, it'll land in stable branch soon. Created attachment 288897 [details]
Fix for the restart from Windows 10 issue
|
Created attachment 286307 [details] dmesg after reboot from Windows 10 I am on Lenovo Thinkpad T495. Since kernel version 5.4.1 I am getting strange issues related to MMC/SDHCI after direct reboot from Microsoft Windows 10, which are manifested by slow system response, a few kernel workers using 100% of CPU, and plenty of SDHCI register dumps in dmesg. If the laptop is powered off first, and then booted to Linux, no problems occur. I am attaching dmesg after reboot from Windows and after clean boot. Also top of the hungry processes is attached.