<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=109246#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=109246">bug 109246</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>From the Xorg log file: [ 212.439] (II) AMDGPU(0): Allocate new frame buffer 1440x900 [ 212.439] (II) AMDGPU(0): => pitch 6144 bytes [ 212.639] (II) AMDGPU(0): Allocate new frame buffer 3360x1080 [ 212.639] (II) AMDGPU(0): => pitch 14336 bytes This does look like there are hotplug events, and the HDMI output is considered disconnected for a moment. (In reply to Alex Deucher from <a href="show_bug.cgi?id=109246#c5">comment #5</a>) > Some monitors poll inputs which sometimes causes the hpd pin to fire which > looks like a hotplug event to the driver. Any idea why this seems to only cause trouble with DC though? (I was seeing similar symptoms with DC and an HDMI connection with Kaveri, I reported it to the DC developers internally a while ago; it's one reason why I'm currently not using DC on this machine)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>