[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 #90 from Rong Zhang (i@rong.moe) ---
(In reply to Rick from comment #89)
> As there is now more output into the dmesg window I decided to capture just
> the system sitting alone through two pause events and captured that in my
> first upload #310145

The EC query was \_SB.PCI0.LPC0.EC0._Q0B. It indeed notifies BAT0 twice!

Method (_Q0B, 0, NotSerialized)  // _Qxx: EC Query, xx=0x00-0xFF
{
    M459 ("Q0B Event\n", 0x00)
    P80H = 0x0B
    If ((Acquire (ECMT, 0x2000) == 0x00))
    {
        Notify (BAT0, 0x80) // Status Change
        Notify (BAT0, 0x81) // Information Change
        Release (ECMT)
    }
}

> 
> Next I did the spamming requested (both l and w alternating until the pause
> ended)
> This is contained in attachment #310146 [details]
> 
> I noticed with the first spamming attempt that the new output ACPI messages
> happen in the dmesg window before the system actually pauses.  So I did
> another spamming attempt but this time I tried to start spamming as soon as
> I saw the dmesg window start displaying the new ACPI messages.  It is likely
> this file has data that starts earlier and personally I would start looking
> at this one first.
> This is contained in attachment #310147 [details]

Thanks. They look fine. At first glance, I did find some new information that
confirmed my previous assumptions. I will find some time looking into them
carefully.

> 
> As always - let me know if you want more.

The current ones should be enough. Now I already have some thoughts on how to
improve battery event handling. The current code path is really awful and
"contributes" quite a bit to the unfortunate combination of FW and SW bugs.

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

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