https://bugs.freedesktop.org/show_bug.cgi?id=98324
Bug ID: 98324 Summary: amd-staging-4.7: problems with unblanking displays when monitors are switched off Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: bugspam@moreofthesa.me.uk
Created attachment 127405 --> https://bugs.freedesktop.org/attachment.cgi?id=127405&action=edit Kernel log extract, showing the unblanking failure.
Setup: RX 470 with two monitors attached – one via DVI-and one via HDMI. (Both are AOC monitors.)
* Ensure that outputs are blanked (via xset, time-out or similar). * Switch off the monitors. * Unblank the outputs. * Switch on the monitors.
Invariably, in this situation, the DVI-connected monitor is unblanked and displaying what it should be, but the HDMI-connected monitor is receiving no signal (or at least nothing to display) and is therefore displaying nothing.
The HDMI-connected monitor can be restored by using xrandr to change mode or by blanking and unblanking – so long as it's switched on while doing so.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Darren Salt bugspam@moreofthesa.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 (AMD64) OS|All |Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #1 from dwagner jb5sgc1n.nya@20mm.eu --- JFYI: A similar, but more dramatic symptom that may be related I reported in https://bugs.freedesktop.org/show_bug.cgi?id=102323
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|amd-staging-4.7: problems |[DC] amd-staging-4.7: |with unblanking displays |problems with unblanking |when monitors are switched |displays when monitors are |off |switched off CC| |harry.wentland@amd.com
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #2 from Darren Salt bugspam@moreofthesa.me.uk --- Currently running amd-staging-drm-next 0313e8bfbbdd. The behaviour is now improved, though is still regressed vs. mainline.
Unblanking works. If I allow the problem monitor to display “no signal”, it becomes effectively disconnected, and becomes reconnected (as if physically freshly connected) on unblanking.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #3 from Darren Salt bugspam@moreofthesa.me.uk --- Created attachment 133671 --> https://bugs.freedesktop.org/attachment.cgi?id=133671&action=edit Kernel log showing normal blank & unblank.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Darren Salt bugspam@moreofthesa.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #127405|0 |1 is obsolete| |
--- Comment #4 from Darren Salt bugspam@moreofthesa.me.uk --- Created attachment 133673 --> https://bugs.freedesktop.org/attachment.cgi?id=133673&action=edit Kernel log showing blanking & as-if-reconnected unblanking.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #5 from dwagner jb5sgc1n.nya@20mm.eu --- JFYI: A patch attached to report https://bugs.freedesktop.org/show_bug.cgi?id=102323 provided some improved behaviour regarding switched-off HDMI displays.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #6 from Darren Salt bugspam@moreofthesa.me.uk --- That patch makes no difference to this problem.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #7 from Darren Salt bugspam@moreofthesa.me.uk --- Seems to be working properly with current amd-staging-drm-next (43dd6fde5df4).
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #8 from Darren Salt bugspam@moreofthesa.me.uk --- Broken (same symptoms, though the kernel log looks a little different) with drm-next-4.15-dc (fbf0c14dd75) (merged with 4.13.4).
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #9 from Darren Salt bugspam@moreofthesa.me.uk --- Created attachment 134594 --> https://bugs.freedesktop.org/attachment.cgi?id=134594&action=edit Apparent EDID errors
HDMI monitor set to 1920×1080, but on unblanking gets set to 1152×864.
This is the second time that I've seen this. Both times it's happened on the first unblanking after boot; both times, using drm-next-4.15-dc.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #10 from Darren Salt bugspam@moreofthesa.me.uk --- Created attachment 139325 --> https://bugs.freedesktop.org/attachment.cgi?id=139325&action=edit Good EDID output (4.17-rc3 + DC)
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #11 from Darren Salt bugspam@moreofthesa.me.uk --- Created attachment 139326 --> https://bugs.freedesktop.org/attachment.cgi?id=139326&action=edit Bad EDID output (4.17-rc3 + DC)
Once this happens (after VESA blanking long enough for the problem monitor to fully go to sleep), it persists until reboot.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #12 from Edward Kigwana edwardwwgk@gmail.com --- I remember this having this issue and found that switching to the console (CTRL-ALT-F1) and then back to X once or twice woke the monitor.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #13 from Darren Salt bugspam@moreofthesa.me.uk --- EDID problems are gone in drm-next-4.18. However, the disconnection issue remains.
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #14 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/108.
dri-devel@lists.freedesktop.org