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: Fri, 10 Jul 2026 21:08:32 +0000 [thread overview]
Message-ID: <bug-221065-215701-J27NiTJ4nU@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 #100 from Rong Zhang (i@rong.moe) ---
(In reply to Avraham Hollander from comment #99)
> Hmm. I'm still getting a little bit of spam from ucsi_acpi. I got the same
> "ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-5)" as well as
> "ucsi_acpi USBC000:00: unknown error 0." I did re-enable the ucsi_acpi
> driver though. I'm inclined to just disable it. I don't think it really
> provides anything for me other than knowing which port the charger is
> plugged into. Charger state is already handled by ACPI_AC.
Thanks for the tag!
My series aims to reduce the pressure on the broken mutex and hence reduce the
probability of triggering the mutex bug. It cannot miraculously fix all dmesg
spamming. As long as it reduces some dmesg messages and/or system freeze, it
works as expected. A proper fix will be a BIOS update, but unfortunately we
haven't heard good news about it.
And it seems that whether seeing the ucsi_acpi spamming depends on models. Some
folks in the thread rarely see it while others see it more frequently, IIRC.
I actually tried to submit a patch to disable ucsi_acpi on devices with the
mutex bug. It is never merged as Mark wanted some more time for the FW team to
investigate the issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-07-10 21:08 UTC|newest]
Thread overview: 104+ 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
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
2026-04-11 18:57 ` bugzilla-daemon
2026-04-24 22:09 ` bugzilla-daemon
2026-04-26 18:39 ` bugzilla-daemon
2026-04-26 18:43 ` bugzilla-daemon
2026-04-26 18:44 ` bugzilla-daemon
2026-04-26 18:50 ` bugzilla-daemon
2026-04-26 19:08 ` bugzilla-daemon
2026-04-26 19:21 ` bugzilla-daemon
2026-04-27 5:42 ` bugzilla-daemon
2026-04-27 11:50 ` bugzilla-daemon
2026-04-27 12:21 ` bugzilla-daemon
2026-04-27 12:34 ` bugzilla-daemon
2026-04-27 23:58 ` bugzilla-daemon
2026-04-28 9:01 ` bugzilla-daemon
2026-04-28 12:22 ` bugzilla-daemon
2026-04-30 9:30 ` bugzilla-daemon
2026-04-30 17:20 ` bugzilla-daemon
2026-05-14 17:39 ` bugzilla-daemon
2026-05-15 19:58 ` bugzilla-daemon
2026-05-15 22:09 ` bugzilla-daemon
2026-05-15 22:30 ` bugzilla-daemon
2026-05-16 17:37 ` bugzilla-daemon
2026-05-16 17:47 ` bugzilla-daemon
2026-05-16 21:02 ` bugzilla-daemon
2026-05-16 22:21 ` bugzilla-daemon
2026-05-17 1:12 ` bugzilla-daemon
2026-05-17 16:45 ` bugzilla-daemon
2026-05-17 21:32 ` bugzilla-daemon
2026-05-17 21:33 ` bugzilla-daemon
2026-05-17 21:33 ` bugzilla-daemon
2026-05-17 21:48 ` bugzilla-daemon
2026-05-18 16:48 ` bugzilla-daemon
2026-05-20 15:43 ` bugzilla-daemon
2026-05-20 15:46 ` bugzilla-daemon
2026-05-25 12:14 ` bugzilla-daemon
2026-05-25 17:30 ` bugzilla-daemon
2026-05-26 12:33 ` bugzilla-daemon
2026-06-26 7:33 ` bugzilla-daemon
2026-07-03 16:53 ` bugzilla-daemon
2026-07-10 18:02 ` bugzilla-daemon
2026-07-10 20:30 ` bugzilla-daemon
2026-07-10 21:08 ` bugzilla-daemon [this message]
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-J27NiTJ4nU@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.