mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: s2idle stopped working with 6.6-rc on Thinkpad T14 G1 (AMD)
Date: Mon, 25 Sep 2023 08:25:31 -0500	[thread overview]
Message-ID: <e556ae63-0539-4b34-b33f-5f5beb4183d1@amd.com> (raw)
In-Reply-To: <0d84fb59-4628-4c7f-ab1a-f58889ef2c9b@leemhuis.info>

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.  I've personally done s2idle 
on 6.6-rc1 + patch to fix the UCSI issue and 6.6-rc2 on a newer model 
(Lenovo Z13).

I haven't checked 6.6-rc3.

> I'm as of now not sure
> exactly when the problem started, as 6.6-rc1 didn't boot for me due to
> another regression fixed for -rc2. But 6.6-rc2 was affected and -rc3
> still is. Haven't found time for a bisection yet and will unlikely to be
> so in the next two or three days, that's why I thought "ask Mario, with
> a bit of luck he might be aware of a problem or even a fix".
> 

For any bisect steps that are failing to boot, I suggest you either 
compile without UCSI support (it shouldn't be critical) or apply

f26a679ed799 ("usb: typec: ucsi: Fix NULL pointer dereference")

> FWIW, I ran your amd_s2idle.py script, but the machine seems to lock up
> hard on resume, so I guess it's not much or help.
> 
> https://www.leemhuis.info/files/misc/s2idle_report-6.5.4-2023-09-25.txt
> https://www.leemhuis.info/files/misc/s2idle_report-6.6_rc3-2023-09-25.txt
> 

Yeah not too much useful stuff here unfortunately.  Can you check 
/var/lib/systemd/pstore to see if you got a traceback for whatever 
caused the problem?

> Dmesg for 6.6-rc3 (with a USB-C dock, but problem happens without it, too):
> https://www.leemhuis.info/files/misc/dmesg-6.6_rc3
> 
> Ciao, Thorsten
> 
> #regzbot introduced v6.5..v6.6-rc2

Being G1, can you try "amdgpu.mcbp=0" on kernel command line?


  reply	other threads:[~2023-09-25 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 10:55 Thorsten Leemhuis
2023-09-25 13:25 ` Mario Limonciello [this message]
2023-09-25 13:45   ` Thorsten Leemhuis
2023-09-25 17:44     ` Mario Limonciello
2023-09-27  8:55       ` Linux regression tracking (Thorsten Leemhuis)
2023-09-27  8:57       ` Thorsten Leemhuis
2023-09-27 13:13         ` Mario Limonciello

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e556ae63-0539-4b34-b33f-5f5beb4183d1@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®