linux-kernel - Re: s2idle stopped working with 6.6-rc on Thinkpad T14 G1 (AMD)

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a1070c38-5a06-479a-bd3f-35bd34ee9fe2@amd.com>
Date:   Wed, 27 Sep 2023 08:13:20 -0500
From:   Mario Limonciello <mario.limonciello@....com>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>
Cc:     Linux PM <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: s2idle stopped working with 6.6-rc on Thinkpad T14 G1 (AMD)

On 9/27/2023 03:57, Thorsten Leemhuis wrote:
> [one more time, please ignore the previous message]
> 
> On 25.09.23 19:44, Mario Limonciello wrote:
>> On 9/25/2023 08:45, Thorsten Leemhuis wrote:
>>> On 25.09.23 15:25, Mario Limonciello wrote:
>>>> On 9/25/2023 05:55, Thorsten Leemhuis wrote:
>>>>> Hi Mario! Did you by chance hear anything about lock-ups on resume with
>>>>> mainline affecting AMD systems? I'm asking, as s2idle stopped working
>>>>> for me with 6.6-rc on my Thinkpad T14 G1 (AMD).
>>>> You're the first report I've heard of this.
>>> Thx for taking the time and replying.
>> [...]
>> FWIW your email prompted me to double check the two other Lenovo systems
>> I have on hand at my desk:
>> * P14s Gen 1
>> * L14 Gen2a
>>
>> One of them had a Ubuntu userspace (20.04 IIRC) and the other a Fedora
>> 38.  I built 6.6-rc3 and couldn't reproduce any issues with s2idle.
>>
>> So yes; bisect is the next step, thanks.
> 
> Thx again for your work.
> 
> FWIW, turned out the problem is caused by 92e24e0e57f72e ("Input:
> psmouse - add delay when deactivating for SMBus mode"). Guess it's a
> timing issue. Reported it in a new thread:
> 
> #regzbot dup-of:
> https://lore.kernel.org/regressions/ca0109fa-c64b-43c1-a651-75b294d750a1@leemhuis.info/
> 
> Ciao, Thorsten
> 
> 
> 
> 

Sounds good, thanks for letting me know.