[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

Additional data (resume failure analysis)

Hardware:
- GPU: AMD Radeon R9 380 (Tonga, GCN 3)
- CPU: AMD Ryzen 5 5500
- RAM: 16 GB
- Display: HDMI

Software:
- Kernel: 6.8.0-106-generic
- Driver: amdgpu
- Display server: X11 (issue reproducible), Wayland (no hard failure)

---

Summary:

After suspend/resume, HDMI output is not restored and the system may
freeze under X11.

The issue is reproducible and was not present in Linux 6.3.

---

Key observation:

During resume, the driver fails to read EDID:

amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.

This appears to explain why HDMI output is not restored.

---

Relevant DRM / AMDGPU log excerpt:

[drm] Display Core v3.2.266 initialized on DCE 10.0
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
[drm] Initialized amdgpu 3.57.0 20150101 for 0000:01:00.0

---

Analysis:

- The failure occurs during display reinitialization after resume
- EDID read failure prevents proper HDMI modeset
- This aligns with the observed "no signal" condition

Behavior differences:

- deep sleep:
- full GPU/display reinitialization
- leads to EDID failure and system instability

- s2idle:
- partial resume
- avoids full lockup but display may still be inconsistent

This suggests the issue is in the display resume path, possibly
involving:

- DC state restore
- HDMI link training
- DDC/EDID communication
- atomic modeset reconstruction

---

Conclusion:

This is likely a regression in the AMDGPU display resume path, where
EDID read fails after resume, preventing HDMI output from being
restored.

---

Additional notes:

This issue was bisected between Linux 6.3 (good) and 6.4 (bad), with the
transition point identified as a KVM merge commit. While not directly
related to AMDGPU, it may have indirectly exposed this issue via
timing/order changes.

---

If needed, I can provide:

- full journalctl logs
- full bisect log
- additional testing (kernel params, debug options)

--
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