From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221421] New: amdgpu fails to display anything after resume from S3 suspend
Date: Sun, 26 Apr 2026 23:25:09 +0000 [thread overview]
Message-ID: <bug-221421-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221421
Bug ID: 221421
Summary: amdgpu fails to display anything after resume from S3
suspend
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: 0456523@gmail.com
Regression: No
Hardware:
Machine: Dell Inspiron 15 3525
CPU: AMD Ryzen 7 5825U
GPU: AMD Barcelo [Integrated]
RAM: 16GB (2x8GB) of RAM, 32GB of swap
Distro: Arch Linux
Current kernel version: 6.19.14
This laptop originally did not advertise S3 sleep support in the DSDT. S0ix was
chewing up my battery so I followed a guide like this
(https://dev.to/epassaro/fix-suspend-issues-on-dell-7405-2-in-1-3l1b) to patch
S3 sleep back in. I still have the files from back when I did that if they are
needed. Another issue is that the touchpad also will immediately wake the
laptop back up with no interaction (which I fixed with a udev rule that matches
the touchpad by name and sets ATTR{power/wakeup}="disabled"), but that's a
separate issue.
Steps to reproduce and what happens:
1. Start up
2. Log in to TTY
3. Run systemctl suspend
4. Display goes black and backlight turns off, and the system goes to sleep
5. Wake the system up by hitting a key
6. System wakes up
7. Backlight turns on
8. Display remains black
This only happens when resuming from S3 sleep and does not happen when resuming
from S0ix or hibernation.
There are a few things that worked or used to work to restore the image on the
display:
Connecting an external display will produce an image on the external display
just fine, and changing the resolution of the main display worked in restoring
the image to it last time I tried, but having to grab my spare monitor out of
the closet and hook it up is a massive pain.
Doing sudo cat /sys/kernel/debug/dri/128/amdgpu_gpu_recover used to work
sometimes, but it seems to now have no effect other than toggling the backlight
off then back on.
I have also tried passing in acpi.prefer_microsoft_guid=1 and
amdgpu.dcdebugmask=0x10 during boot but neither had any effect at all (good or
bad). I checked the kernel logs and there does not seem to be any obvious
errors (amdgpu-related or not) when suspending and resuming.
This is a massive pain since S0ix or hibernation are the only 2 ways to avoid a
black screen on resume, but S0ix is unusably power-draining, and hibernation is
still considerably slower than it is on Windows.
--
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:[~2026-04-26 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 23:25 bugzilla-daemon [this message]
2026-04-27 7:50 ` [Bug 221421] amdgpu fails to display anything after resume from S3 suspend 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-221421-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox