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: Sat, 16 May 2026 17:37:54 +0000 [thread overview]
Message-ID: <bug-221065-215701-sMzqgVJp90@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 #80 from Rong Zhang (i@rong.moe) ---
(In reply to Rick from comment #78)
> (In reply to Rong Zhang from comment #77)
> > (In reply to Rick from comment #76)
> > Hmm, interesting. I assume the pauses had existed before I introduced the
> > warning message (unexpected charge_types...), right?
>
> Correct - this pause happens in Kernel 6.17 with no messages, when I load
> Kernel 6.19 I started getting the messages and that lead me to this thread.
> I tried Kernel 6.16 and the pause does not happen - so I believe this
> behavior was introduced in Kernel 6.17
Oh, that was when the charge_types attribute was added to ideapad-laptop.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da8f2708f9b69707f4efeb432a18395e46b4666f
> > This sounds like a slow SMI handling due to the broken firmware.
> >
> > Could you kindly provide more detailed information about the pause? When it
> > happened, did you notice a spike in CPU usage? Did you see any dmesg
> message
> > at that time? Did it freeze your system completely or just make things
> laggy?
>
> The system appears to freeze solid for about 1 to 2 seconds (hard to tell
> the exact timing - but the pause feels like it is always the same duration).
> Nothing on screen changes.
>
> When running system monitor during the event I see it freeze but when it
> restarts I don't see any spikes or anything interesting on any graph.
Did it have a power consumption graph and a CPU frequency graph? I will talk
more about monitoring later.
>
> When I was running the "perf stat" stuff below I did notice that during the
> freeze it stopped updating and when it resumed it looked like it filled in
> all the data that was paused. Normally the perf stat seems to just produce a
> row of data on a periodic basis and when the pause happens it stops but
> after the freeze it looks like it prints a bunch of rows to catch up to
> where it should be.
>
> There is no laggy behavior either before or after the freeze. The system
> works perfectly at all times except for the duration of the freeze.
>
> No message in dmesg under Kernel 6.17 (the default kernel in Mint - my daily
> driver).
>
> The dmesg message shows up (Kernel 6.19 used for this) as soon as the freeze
> is finished (here are three consecutive events captured using "dmesg -w" so
> you can see the timing between them:
> [ 107.554265] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast]
> and [Long_Life] are enabled
> [ 501.851737] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast]
> and [Long_Life] are enabled
> [ 933.076412] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast]
> and [Long_Life] are enabled
So I speculate that some userspace utilities (probably upower or the desktop
environment?) read charge_types regularly or upon power events. Before v6.17,
ideapad-laptop didn't support it, so nothing could be read. However, since
v6.17, they can actually read it, and reading it triggers ECMT chaos upon power
events.
>
> >
> > Could you also monitor the SMI count, i.e.,
> >
> > sudo perf stat -e ls_smi_rx -I 1000
> >
> > ..., wait for the pause to occur, and check how many SMIs have occurred
> > during the pause?
>
> There number stayed at 0 the entire time I was testing the pause - the pause
> did not make the number increment.
Hmm, that's weird...
> Let me clarify this - After further testing: the mouse cursor continues to
> move on screen during a pause event.
Thanks a lot for the information. It's very helpful.
I suppose it could be a CPU/GPU throttle that delayed some rendering work. On
modern desktop environments, the cursor is rendered on a different layer --
that may be why it continues to move.
> For testing I was in a text editor scrolling a long document up and down
> (using mouse wheel) while moving the mouse in a circle. When the pause
> happens the document stops scrolling and the performance monitor stops
> updating.
>
> During the freeze the mouse cursor stayed fully responsive to my movements
> and did not seem laggy or out of the ordinary.
>
> For reference I am running Linux Mint 22.3 - Cinnamon 64-bit - Cinnamon 6.6.7
>
> I was also typing this comment with the ideapad_laptop kernel module enabled
> and I think the pause also allows keyboard input to buffer and not be
> ignored. (I was typing when a pause happened and I could have sworn that a
> key didn't register on screen so I hit it again and when the pause ended I
> ended up with two of the characters).
Sounds like rendering delays, too. Such rendering delays usually don't freeze
remote shells, e.g., SSH.
Could you try monitoring your laptop using s-tui? You would need to run it as
root so that it can read the power consumption. The refresh interval should be
set to 0.5s so that you can see measurements during pause events.
If possible, please SSH to your laptop from another PC and watch s-tui from the
latter so that you can immediately see what's happening during the pause.
It would also be helpful to monitor twice with s-tui: once with its stress
feature on and once with it off.
If you have enough time to mess around with pause event, could you also check
if it freezes virtual terminals (use the kernel one instead of kmscon)? I guess
it won't.
You may also try to SSH to your laptop from another PC or your smartphone, type
`echo l | sudo tee /proc/sysrq-trigger' in the shell, wait for a pause event,
and press Enter immediately. This should reveal what processes are running and
what the kernel is doing during the event. `echo w | sudo tee
/proc/sysrq-trigger' would also be helpful, as it reveals what processes are
blocked during the pause.
--
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-05-16 17:37 UTC|newest]
Thread overview: 99+ 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 [this message]
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
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-sMzqgVJp90@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.