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

Hi @agd5f and @Venemo, I appreciate the technical feedback, but I must respectfully disagree with the "normal behavior" assessment for one simple, documented reason: The 6.1.169 LTS Baseline. I have performed a controlled test using the same hardware, same OS, and same logging levels. The "Logging Enabled" Argument: If the flood of amdgpu_dm_atomic_commit_tail messages were merely due to logging being enabled, they should appear in the Kernel 6.1 logs as well. They do not. On Kernel 6.1, the driver is silent and efficient after resume. On 6.4+, it enters a frantic infinite loop. Why does "normal compositor behavior" only become "spammy" from 6.4 onwards? The "Monitor Specific" Argument: If the HDMI signal drop were a hardware or monitor issue, it would manifest regardless of the kernel version. The signal is rock solid on Kernel 6.1. It only drops on kernels that exhibit the 200MB/min log flooding. This is a software- induced signal failure, not a hardware defect. The Challenge: I am more than willing to perform a bisect to find the exact commit that broke Tonga, but I am blocked by the infrastructure. The Ubuntu Mainline servers return 404 Not Found for the 6.4-rc series. Since you requested a bisect: Can you provide a valid, working link to the 6.4-rc1 (and subsequent RCs) binaries compatible with Ubuntu/Zorin? Or, can you point to the specific changes in DC/Atomic State handling for Volcanic Islands that landed in 6.4? I have the data. I have the "Good" (6.1) and the "Bad" (6.4+). I am ready to test, but I need valid tools. Until then, the logs clearly show a regression that started in the 6.4 cycle. Best regards, Danilo (The Tonga Guy) -- 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