https://gitlab.freedesktop.org/drm/amd/-/work_items/5123
Hi all, Quick update: The issue is still reproducible without the workaround. Observed behavior: After suspend/resume or DPMS, EDID read may fail initially The monitor becomes responsive shortly after The display state is not revalidated automatically A delayed manual reinitialization (off → on) consistently restores correct behavior This points to a likely missing retry or revalidation step after an initial EDID failure during resume. I can reproduce this reliably without the workaround and provide targeted logs (e.g. drm.debug) or test specific scenarios if that would help validate a proper fix. Please let me know what would be most useful. I would like to briefly check if there is still interest in investigating this issue. I’ve spent time narrowing it down (including bisect, testing multiple kernels, and isolating behavior), and I’m still able to reproduce it reliably without the workaround. Current key point: The issue appears to be timing-related during resume / DPMS EDID read may fail initially, but succeeds shortly after The display is not revalidated automatically A delayed manual reinitialization consistently restores correct behavior This suggests a missing retry or revalidation step after resume. I’m very willing to help move this forward — I can: provide clean logs (including drm.debug) test experimental patches run targeted scenarios if needed Just let me know what would be most useful. Thanks for your time and for the work on amdgpu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
