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

bugzilla-daemon
2026-02-11T16:58:51Z

--- Comment #29 from Rong Zhang (i@rong.moe) ---
(In reply to Avraham Hollander from comment #27)

Thanks for your test.

> It did not. Unplugging and replugging the charger a bunch of times results
> in:
> [...]

Ahh, my fault. I meant fixing the issue that ideapad-laptop misinterprets the
error returned by the GBMD method as a valid return value. According to your
log, the patch seems correct.

As for the issue of the mutex chaos (and hence the error logs you got), we
can't really fix it from the kernel side. It can only be fixed by a BIOS
update. That's why I added Mark to the CC list.

I've seen GBMD, SALS, SBMC, and DYTC calling ECCC. I think we will have to add
a DMI quirk disabling most (if not all) features of ideapad-laptop on 83DR
until a BIOS update fixes the mutex bug. Doing so should make the mutex less
likely to break. As a quick test, could you test if blacklisting ideapad-laptop
in modprobe.d (reboot required, ofc) helps?

(In reply to Avraham Hollander from comment #28)
> Is there anything you notice in there that could potentially cause the
> system to take excessively long (2-6 seconds) to resume from s2idle? That's
> another probably ACPI issue that I've always had. This is almost certainly
> unrelated to the charger bug and I don't want to go completely off topic,
> but I figure it's worth mentioning now that I have contact with the relevant
> people.

I guess this is also related to the mutex bug in DSDT, considering it has a
bunch of EC queries calling ECCC. Blacklisting ideapad-laptop may have some
help, as doing so reduces the probability of running into a race condition.

I am not really familiar with s2idle and EC queries, so I may not be the best
person to answer this. Armin, do you have any thoughts?