Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
	Lijo Lazar <lijo.lazar@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Marcel Jira <marcel.jira@gmail.com>,
	Niklas Cathor <niklas.cathor@gmx.de>,
	1114806@bugs.debian.org
Subject: Re: Please backport commit 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset") to v6.16.y
Date: Sun, 14 Sep 2025 14:00:04 +0200	[thread overview]
Message-ID: <aMauROClYgtk9wrq@eldamar.lan> (raw)
In-Reply-To: <2025091431-manpower-osmosis-b679@gregkh>

Hi Greg,

[note fixing up my typo for the Debian bug, sorry about that]

On Sun, Sep 14, 2025 at 01:43:38PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Sep 14, 2025 at 01:18:11PM +0200, Salvatore Bonaccorso wrote:
> > Hi
> > 
> > In Debian we got the report in https://bugs.debian.org/1114806 that
> > suspend to RAM fails (amdgpu driver hang) and Niklas Cathor was both
> > able to bisect the issue down to 8345a71fc54b ("drm/amdgpu: Add more
> > checks to PSP mailbox") (which was backported to 6.12.2 as well).
> > 
> > There is an upstream report as well at
> > https://gitlab.freedesktop.org/drm/amd/-/issues/4531 matching the
> > issue and fixed by 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader
> > after PSPv11 reset").
> > 
> > Unfortunately the commit does not apply cleanly to 6.16.y as well as
> > there were the changes around 9888f73679b7 ("drm/amdgpu: Add a
> > noverbose flag to psp_wait_for").
> > 
> > Attached patch backports the commit due to this context changes,
> > assuming it is not desirable to pick as well 9888f73679b7.
> > 
> > Does that looks good? If yes, can you please consider picking it up or
> > the next 6.16.y stable series as well?
> 
> I have a revert of the offending commit in the 6.16.y queue right now,
> as this was pointed out as causing a problem:
> 	https://lore.kernel.org/all/20250904220457.473940-1-alexander.deucher@amd.com/
> so that should resolve this issue, right?

Ah good, yes that should be equally fine (I missed the pending
revert). Thanks a lot!

Regards,
Salvatore

  reply	other threads:[~2025-09-14 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 11:18 Please backport commit 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset") to v6.16.y Salvatore Bonaccorso
2025-09-14 11:43 ` Greg Kroah-Hartman
2025-09-14 12:00   ` Salvatore Bonaccorso [this message]
2025-09-14 14:48   ` Niklas Cathor

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=aMauROClYgtk9wrq@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1114806@bugs.debian.org \
    --cc=alexander.deucher@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lijo.lazar@amd.com \
    --cc=marcel.jira@gmail.com \
    --cc=niklas.cathor@gmx.de \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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