Message-ID: <d5acb485-7377-4139-826d-4df04d21b5ed@leemhuis.info>
Date: Tue, 5 Nov 2024 17:06:52 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Cc: Michael <auslands-kv@....de>,
 "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
 Linux kernel regressions list <regressions@...ts.linux.dev>,
 LKML <linux-kernel@...r.kernel.org>
Subject: [regression] Bug 219440: Touchscreen stops working after Suspendi:
 i2c_designware.1: controller timed out

Hi, Thorsten here, the Linux kernel's regression tracker.

Jarkko, I noticed a report about a regression in bugzilla.kernel.org
that appears to be related to i2c_designware (at least it looks like
that to my untrained eyes). As many (most?) kernel developers don't keep
an eye on the bug tracker, I decided to write this mail. To quote from
https://bugzilla.kernel.org/show_bug.cgi?id=219440 :

>  Michael 2024-10-29 08:43:55 UTC
>
> Just noticed that the touchscreen on my ASUS vivobook S14 stops
> working after a suspend-to-idle. As this is something, I clearly
> didn't have before, I tested every kernel version released in the
> last six months and found the kernel, where the bug was introduced:
> 6.10. The last 6.9.12 is still working correctly. Since 6.10 all
> kernel versions have the problem.
> 
> Some more info:
> 
> Hardware: ASUS Vivobook S14 (TP3402VA) Kernel working: up to 6.9.12 
> Kernel defect: from 6.10 OS: nixos
> 
> I do not have much knowledge about the input devices. I tested that
> i2c_hid_acpi seems to be relevant for the touchscreen (and also the
> touchpad), as, when I remove it, both stop working. Reloading the
> kernel module restores functionality (but NOT after a suspend-to-
> idle!!!). Otherwise, I do not see any error messages or so. (Or do
> not recognize them...)
> 
> Any help I can offer to identify the regression bug?

[...]

> 6.12-rc4 does not work either. The regression started with 6.10.

[...]

> i2c_designware i2c_designware.1: controller timed out
> i2c_designware i2c_designware.1: timeout in disabling adapter
> i2c_hid_acpi i2c-WDHT1F01:00: failed to change power setting.
> i2c_hid_acpi i2c-WDHT1F01:00: PM: dpm_run_callback(): acpi_subsys_resume returns -110
> i2c_hid_acpi i2c-WDHT1F01:00: PM: failed to resume async: error -110
[...]

See the ticket for more details. The reporter (Michael) is CCed.

Michael: if this mail is fruitless, you most like need to use git bisect
to find the change that broke things. For details, see:
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
https://docs.kernel.org/admin-guide/bug-bisect.html

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

[1] because bugzilla.kernel.org tells users upon registration their
"email address will never be displayed to logged out users"

P.S.: let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.9..v6.10
#regzbot title: i2c: designware: touchscreen stops working after Suspend
#regzbot from: Michael <auslands-kv@....de>
#regzbot duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=219440
#regzbot ignore-activity

Powered by blists - more mailing lists