[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3efa338a-6d0c-46a9-ae59-d96fbe6aa5af@leemhuis.info>
Date: Wed, 27 Sep 2023 10:55:48 +0200
From: "Linux regression tracking (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)
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. Turns out it was
Powered by blists - more mailing lists