Re: Regression: Mouse gets sluggish after suspend/resume and power usage significant higher after resume

[Thorsten Leemhuis]

On 09.04.22 04:13, Dmitry Torokhov wrote:
> On Fri, Apr 08, 2022 at 03:20:14PM +0200, Thorsten Leemhuis wrote:
>> Hi, this is your Linux kernel regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>> acted upon since it was reported about a week ago, that's why I decided
>> to forward it to the lists and all people that seemed to be relevant
>> here. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=215747 :
> 
> This looks like I2C-HID controller and I see bunch of "incomplete
> report"s in the logs:
> 
> [16558.456434] i2c_hid_acpi i2c-ELAN0670:00: i2c_hid_get_input: incomplete report (14/3583)
> [16558.457434] i2c_hid_acpi i2c-ELAN0670:00: i2c_hid_get_input: incomplete report (14/259)
> [16558.458384] i2c_hid_acpi i2c-ELAN0670:00: i2c_hid_get_input: incomplete report (14/65281)
> 
> Let's add benjamin, Jiri and Jungle...

Thx. There was some discussion in the bko ticket and now it seems like
it's not a regression (sorry for the noise) -- and the root of the
problem apparently is a known firmware issue of the particular laptop:
https://bugzilla.kernel.org/show_bug.cgi?id=214775

Thx again! Ciao, Thorsten

#regzbot invalid: not a regression, see
https://bugzilla.kernel.org/show_bug.cgi?id=215747 for details

>>>  Nico Schottelius 2022-03-26 19:27:06 UTC
>>>
>>> Created attachment 300619 [details]
>>> dmesg
>>>
>>> TL;DR:
>>>
>>> Suspending and resume makes the ELAN0670:00 trackpad sluggish (very hard to move the pointer) and the energy usage of the notebook is about 3 times higher than before suspend.
>>>
>>> Background:
>>>
>>>
>>> On a Lenovo X1 Nano the trackpad works fine until suspend/resume.The estimated battery runtime PRIOR to suspend/resume is 8h 43m. After suspend resume it drops to 2h 20m instantly.
>>>
>>> There seems to be a firmware error in the iwlwifi card show in the attached dmesg, but I am not sure whether "that's enough" to cause both symptoms.
>>>
>>> Kernel is from Alpine Linux, which is basically stock upstream afaics.
>>
>> See later comments for more details. In one of them the reporter states
>> he's pretty sure that it didn't happen with 5.13.
>>
>> Not sure if this is input, PM, bluetooth, or something else. But sounds
>> like a problem in the input code to me (you have to start somewhere...).
>>
>> Could somebody take a look into this? Or was this discussed somewhere
>> else already? Or even fixed?
>>
>> Anyway, to get this tracked:
>>
>> #regzbot introduced: v5.13..v5.15.31	
>> #regzbot from: Nico Schottelius  <nico-bugzilla.kernel.org@xxxxxxxxxxxxxxx>
>> #regzbot title: input: Mouse gets sluggish after suspend/resume and
>> power usage significant higher after resume
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215747
>>
>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>
>> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
>> reports on my table. I can only look briefly into most of them and lack
>> knowledge about most of the areas they concern. I thus unfortunately
>> will sometimes get things wrong or miss something important. I hope
>> that's not the case here; if you think it is, don't hesitate to tell me
>> in a public reply, it's in everyone's interest to set the public record
>> straight.
>>
>> -- 
>> Additional information about regzbot:
>>
>> If you want to know more about regzbot, check out its web-interface, the
>> getting start guide, and the references documentation:
>>
>> https://linux-regtracking.leemhuis.info/regzbot/
>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
>>
>> The last two documents will explain how you can interact with regzbot
>> yourself if your want to.
>>
>> Hint for reporters: when reporting a regression it's in your interest to
>> CC the regression list and tell regzbot about the issue, as that ensures
>> the regression makes it onto the radar of the Linux kernel's regression
>> tracker -- that's in your interest, as it ensures your report won't fall
>> through the cracks unnoticed.
>>
>> Hint for developers: you normally don't need to care about regzbot once
>> it's involved. Fix the issue as you normally would, just remember to
>> include 'Link:' tag in the patch descriptions pointing to all reports
>> about the issue. This has been expected from developers even before
>> regzbot showed up for reasons explained in
>> 'Documentation/process/submitting-patches.rst' and
>> 'Documentation/process/5.Posting.rst'.
>