public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221065] ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9
Date: Wed, 11 Feb 2026 18:04:44 +0000	[thread overview]
Message-ID: <bug-221065-215701-GkWYbIyKoi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221065-215701@https.bugzilla.kernel.org/>

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

--- Comment #32 from Avraham Hollander (anhollander516@gmail.com) ---
(In reply to Avraham Hollander from comment #31)
> (In reply to Rong Zhang from comment #29)
> > (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?
> 
> I can't get it to trigger either way now, whether ideapad_laptop is loaded
> or not. Could the cause be that my battery is fully charged now? I'm going
> to discharge it some and try it again.

Actually, it just seems to be really intermittent. Now I'm getting the errors
from ucsi_acpi but not the mutex error, with ideapad_laptop loaded. It's hard
to say for sure whether blacklisting the module helps or not.

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

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

  parent reply	other threads:[~2026-02-11 18:04 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  7:50 [Bug 221065] New: ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9 bugzilla-daemon
2026-02-09  9:10 ` [Bug 221065] " bugzilla-daemon
2026-02-09 11:47 ` bugzilla-daemon
2026-02-09 12:06 ` [Bug 221065] New: " Rong Zhang
2026-02-09 12:11 ` [Bug 221065] " bugzilla-daemon
2026-02-10 17:56 ` bugzilla-daemon
2026-02-10 18:44   ` Rong Zhang
2026-02-10 17:56 ` bugzilla-daemon
2026-02-10 17:57 ` bugzilla-daemon
2026-02-10 18:49 ` bugzilla-daemon
2026-02-10 18:57 ` bugzilla-daemon
2026-02-10 18:58 ` bugzilla-daemon
2026-02-10 19:01 ` bugzilla-daemon
2026-02-10 19:17 ` bugzilla-daemon
2026-02-10 19:23 ` bugzilla-daemon
2026-02-10 19:25 ` bugzilla-daemon
2026-02-10 19:28 ` bugzilla-daemon
2026-02-10 21:20 ` bugzilla-daemon
2026-02-10 21:28 ` bugzilla-daemon
2026-02-10 21:30 ` bugzilla-daemon
2026-02-10 21:32 ` bugzilla-daemon
2026-02-10 21:39 ` bugzilla-daemon
2026-02-10 21:42 ` bugzilla-daemon
2026-02-10 21:43 ` bugzilla-daemon
2026-02-10 21:53 ` bugzilla-daemon
2026-02-11 14:13 ` bugzilla-daemon
2026-02-11 15:02 ` bugzilla-daemon
2026-02-11 15:03 ` bugzilla-daemon
2026-02-11 15:17 ` bugzilla-daemon
2026-02-11 15:17 ` bugzilla-daemon
2026-02-11 15:35 ` bugzilla-daemon
2026-02-11 15:41 ` bugzilla-daemon
2026-02-11 16:58 ` bugzilla-daemon
2026-02-11 17:32 ` bugzilla-daemon
2026-02-11 17:59 ` bugzilla-daemon
2026-02-11 18:04 ` bugzilla-daemon [this message]
2026-02-13 13:20 ` bugzilla-daemon
2026-02-13 13:22 ` bugzilla-daemon
2026-02-17  1:37 ` bugzilla-daemon
2026-02-17  1:59 ` bugzilla-daemon
2026-02-17  2:06 ` bugzilla-daemon
2026-02-17  2:32 ` bugzilla-daemon
2026-02-17  2:44 ` bugzilla-daemon
2026-02-17  2:44 ` bugzilla-daemon
2026-02-17 16:28 ` bugzilla-daemon
2026-03-02 10:56 ` bugzilla-daemon
2026-03-02 11:06 ` bugzilla-daemon
2026-03-02 13:45 ` bugzilla-daemon
2026-03-02 14:41 ` bugzilla-daemon
2026-03-02 16:24 ` bugzilla-daemon
2026-03-02 16:35 ` bugzilla-daemon
2026-03-04 18:25 ` bugzilla-daemon
2026-03-04 18:29 ` bugzilla-daemon
2026-03-09  9:19 ` bugzilla-daemon
2026-03-10 18:01 ` bugzilla-daemon
2026-03-24 10:41 ` bugzilla-daemon
2026-03-24 18:40 ` bugzilla-daemon
2026-03-24 18:48 ` bugzilla-daemon
2026-04-01 12:58 ` bugzilla-daemon
2026-04-01 13:35 ` bugzilla-daemon
2026-04-07 19:02 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-221065-215701-GkWYbIyKoi@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox