Additional structured testing results (regression window identified):
After systematic testing across multiple mainline kernels, I was able to
narrow the behavior down more precisely.
Hardware:
- GPU: AMD Radeon R9 380 (Tonga, amdgpu)
- HDMI connection
- Motherboard: Gigabyte B450 AORUS PRO WIFI
- CPU: Ryzen 5 5500
- Session: X11
Kernel comparison (mainline builds):
6.12.74 (LTS series):
- System fully stable.
- HDMI works normally.
- Suspend/resume works reliably (multiple cycles tested).
- No EDID errors observed.
- No black screen after resume.
6.13.12:
- First suspend/resume usually succeeds.
- Second suspend often fails: black screen, no HDMI signal.
- Keyboard becomes unresponsive.
- Requires hard reboot.
- Intermittent behavior.
6.14.x and newer (including 6.17 previously tested):
- More frequent suspend failures.
- Black screen on resume.
- Occasional "HDMI Out of Range" message during early boot.
- dmesg previously showed:
amdgpu: [drm] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
Important observation:
6.12 works reliably without forcing amdgpu.dc=0.
The issue appears between 6.12 → 6.13, suggesting a regression introduced in that window affecting HDMI reinitialization or EDID handling during resume.
Power state notes:
- Deep (S3) suspend used.
- Forcing s2idle worsened behavior.
- Disabling USB wake reduced spurious wake events but did not solve resume issue.
Conclusion:
This does not appear to be a random hardware instability, as 6.12 remains stable under identical conditions.
The regression likely affects display reinitialization (DC/DRM layer) for Tonga-class GPUs over HDMI.
I am willing to test patches, boot parameters, or debug builds if needed.
My goal is to help narrow this down and contribute useful data for resolving the regression.
Thank you for your work on the kernel and AMDGPU stack.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
Комментариев нет:
Отправить комментарий