lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <7fe4e169-1cf9-2a26-0567-021172dadd3c@leemhuis.info>
Date:   Thu, 30 Mar 2023 15:28:32 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>,
        LKML <linux-kernel@...r.kernel.org>,
        Ike Panhc <ike.pan@...onical.com>,
        Mark Gross <markgross@...nel.org>
Subject: [regression] Bug 217234 - Touchpad disabled after wakeup from sleep
 on Lenovo Yoga 7i 15ITL5 (bisected)

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

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developers don't keep an eye on it, I decided to forward it by mail.

Hans, apparently it's cause by a change of yours.

Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
not CCed them in mails like this.

Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217234 :

>  arsgeiger@...il.com 2023-03-22 23:52:35 UTC
> 
> Created attachment 304002 [details]
> libinput events on linux6.0
> 
> After booting linux6.1 and later upon closing the lid and opening it again, the touchpad is no longer usable. After powering off and booting linux6.0 again (no other changes), the touchpad does continue to work after closing the lid and opening it again.
> 
> When the touchpad gets disabled on linux6.1, after logging in to gnome, I can re-enable it from the settings. Using `libinput debug-events --verbose` Here is a comparison of the output on linux6.0:
> 
>>    2: event10 - lid: suspending touchpad
>> -event1   SWITCH_TOGGLE           +0.000s     switch lid state 1
>>    3: event10 - lid: resume touchpad
>> -event6   KEYBOARD_KEY            +2.164s     KEY_F22 (192) pressed
>>  event6   KEYBOARD_KEY            +2.164s     KEY_F22 (192) released
>>  event6   KEYBOARD_KEY            +2.627s     KEY_F22 (192) pressed
>>  event6   KEYBOARD_KEY            +2.627s     KEY_F22 (192) released
>> -event1   SWITCH_TOGGLE           +2.168s     switch lid state 0
> 
> And linux 6.1+:
> 
>>   2: event10 - lid: suspending touchpad
>> -event1   SWITCH_TOGGLE           +0.000s     switch lid state 1
>>    3: event10 - lid: resume touchpad
>> -event6   KEYBOARD_KEY            +2.000s     KEY_TOUCHPAD_TOGGLE (530)
>> pressed
>>  event6   KEYBOARD_KEY            +2.000s     KEY_TOUCHPAD_TOGGLE (530)
>>  released
>> -event1   SWITCH_TOGGLE           +2.000s     switch lid state 0

> [...]

>  arsgeiger@...il.com 2023-03-30 11:50:11 UTC
> 
> Alright, I found the offending commit (which does not exist in linux6.0 but was backported to linux6.1):
> https://gitlab.com/linux-kernel/stable/-/commit/5829f8a897e4f030cd2d32a930eea8954ab5dcd3
> 
> Building linux6.2 with this commit reverted does workaround the issue for me.

See the ticket for more details.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, 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: 5829f8a897e4f0
https://bugzilla.kernel.org/show_bug.cgi?id=217234
#regzbot title: platform/x86: ideapad-laptop: Touchpad disabled after
wakeup
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

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"

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ