From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220653] New: RX6700XT fails to do S3 resume, then hangup on recovery
Date: Thu, 09 Oct 2025 22:06:40 +0000 [thread overview]
Message-ID: <bug-220653-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220653
Bug ID: 220653
Summary: RX6700XT fails to do S3 resume, then hangup on
recovery
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: blade@debian.org
Regression: No
Created attachment 308784
--> https://bugzilla.kernel.org/attachment.cgi?id=308784&action=edit
S3 suspend failing for RX6700XT
Symptoms:
you try a suspend-to-rum (ACPI-S3) and the system simply doesn't do it, instead
some devices (hdd) wake up again after a few seconds but the system is "in the
limbo", semi-dead, only sync and reboot with magic-sysrq s/u/b works. See
attachment.
Good/bad versions:
Kernels v6.16.x were fine
Kernels v6.17.0-rc<something> started failing
Results of bi-secting: see below.
I didn't want to start bitching around but seriously, for me this kind of
suspend-resume-freeze-fu*up-in-a-RELEASED-kernel has happened a couple of times
now. Isn't there any kind of quality control in AMD's integration team for the
"older" RX 6xxx generation?
± git bisect bad
440cec4ca1c242d72e309a801995584a55af25c6 is the first bad commit
commit 440cec4ca1c242d72e309a801995584a55af25c6 (HEAD)
Author: Lijo Lazar <lijo.lazar@amd.com>
Date: Fri Jul 18 18:50:58 2025 +0530
drm/amdgpu: Wait for bootloader after PSPv11 reset
Some PSPv11 SOCs take a longer time for PSP based mode-1 reset. Instead
of checking for C2PMSG_33 status, add the callback wait_for_bootloader.
Wait for bootloader to be back to steady state is already part of the
generic mode-1 reset flow. Increase the retry count for bootloader wait
and also fix the mask to prevent fake pass.
Fixes: 8345a71fc54b ("drm/amdgpu: Add more checks to PSP mailbox")
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4531
Signed-off-by: Lijo Lazar <lijo.lazar@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 32f73741d6ee41fd5db8791c1163931e313d0fdc)
drivers/gpu/drm/amd/amdgpu/psp_v11_0.c | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-10-09 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 22:06 bugzilla-daemon [this message]
2025-10-09 22:10 ` [Bug 220653] RX6700XT fails to do S3 suspend, then hangup on recovery bugzilla-daemon
2025-10-10 6:02 ` bugzilla-daemon
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=bug-220653-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.