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

[bugzilla-daemon@kernel.org]

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

--- Comment #78 from Rick (rickk1166@gmail.com) ---
(In reply to Rong Zhang from comment #77)
> (In reply to Rick from comment #76)
> > (In reply to jeffrey from comment #74)
> > 
> > I completely blacklisted Ideapad_laptop on my system (using Mint Kernel
> > 6.17.0-23-generic) and this seems to have completely solved the 1 second
> > pauses every 7 minutes for me.
> 
> 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

> 
> 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.

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

> 
> 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.

> 
> You can also mess around with sysfs attributes of ideapad-laptop,
> power_supply, and firmware-attributes to see if reading them causes SMIs:
> 
>   sudo tail /sys/bus/acpi/devices/VPC2004\:00/physical_node/*
>   sudo tail /sys/class/power_supply/*/*
>   sudo tail /sys/class/firmware-attributes/*/attributes/*/*
> 
> On my device, reading /sys/class/firmware-attributes/thinklmi/attributes/*/*
> always causes 580 SMIs, and other attributes do not cause any SMI.

On my device, reading /sys/class/firmware-attributes/thinklmi/attributes/*/*
always causes 504 SMIs, and other attributes do not cause any SMI.

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

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