[Bug 221065] ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=221065

--- Comment #67 from boite.pour.spam@gmail.com ---
I've read all the comments above and I'm trying to understand how the broken
ACPI tables would work on Windows. If there's a "deadlock" in the ACPI
implementation, how does Windows works around it? 
If I understand correctly, the solving options are:
1. Have Lenovo to fix the ACPI tables (which is very unlikely)
2. Implement a "live" ACPI fix with a DSDT override but it won't fix the bad
releasing of the ACPI's mutex (but we can probably live with it, since, except
for the dmesg noise, doesn't break anything)
3. Blacklist both usci_acpi and ideapad-laptop, so that there aren't any
contender on the mutex anymore, but I'm not clear about what's lost when we do
so?

Am I right?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.