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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e3cc6486-48be-46fb-9850-32add544530b@leemhuis.info>
Date:   Wed, 27 Sep 2023 10:57:42 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Mario Limonciello <mario.limonciello@....com>
Cc:     Linux PM <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: s2idle stopped working with 6.6-rc on Thinkpad T14 G1 (AMD)

[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