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: Tue, 17 Feb 2026 01:59:31 +0000 [thread overview]
Message-ID: <bug-221065-215701-DoaX7IIr58@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 #36 from Avraham Hollander (anhollander516@gmail.com) ---
(In reply to Rong Zhang from comment #34)
> I also found some time looking into ucsi_acpi and the AML code of the ACPI
> device (in SSDT17).
>
> Two helper methods (\_SB.PCI0.LPC0.EC0.ECRD for reading,
> \_SB.PCI0.LPC0.EC0.ECWT for writing) are repeatedly called a total of 25 (!)
> times when handling a UCSI command. Their timeout for acquiring the ECMT
> mutex is 1s. Therefore, it is not surprising that some of these calls will
> time out.
>
> Considering this, it seems that ucsi_acpi will cause significant pressure on
> the ECMT mutex, as each UCSI command acquires and releases it 25 times.
> Instead of blacklisting ideapad-laptop, could you try to blacklist
> ucsi_acpi? Doing so should reduce the pressure on the ECMT mutex a lot, so
> other ACPI methods may be less likely to time out. Again, this won't
> completely "fix" the issue, and a BIOS update is the only way to fix it.
>
> Moreover, there is no way for us to determine if any call within them has
> failed, so we can't trust the UCSI ACPI device anymore -- a quirk will also
> be required to disable usci_acpi on 83DR.
I don't *seem* to be getting the mutex error with it blacklisted. However, I'm
still getting the original error from ideapad_acpi.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-02-17 1:59 UTC|newest]
Thread overview: 62+ 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
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 [this message]
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
2026-04-11 18:12 ` 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-DoaX7IIr58@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