<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT]igt/kms_flip/wf_vblank-vs-modeset cause WARNING: CPU: 0 PID: 3716 at drivers/gpu/drm/i915/intel_dp.c:2653 intel_dp_link_down+0x5b/0x18d [i915]()" href="https://bugs.freedesktop.org/show_bug.cgi?id=70570#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT]igt/kms_flip/wf_vblank-vs-modeset cause WARNING: CPU: 0 PID: 3716 at drivers/gpu/drm/i915/intel_dp.c:2653 intel_dp_link_down+0x5b/0x18d [i915]()" href="https://bugs.freedesktop.org/show_bug.cgi?id=70570">bug 70570</a> from <a class="email" href="mailto:imre.deak@gmail.com" title="Imre Deak <imre.deak@gmail.com>"> Imre Deak</a> <pre>Created <a href="attachment.cgi?id=92023" name="attach_92023" title="don't disable DP port during hot unplug">attachment 92023</a> <a href="attachment.cgi?id=92023&action=edit" title="don't disable DP port during hot unplug">[details]</a> <a href='page.cgi?id=splinter.html&bug=70570&attachment=92023'>[review]</a> don't disable DP port during hot unplug I hit the same WARN by first unplugging the DP cable and then doing an xrandr --off. The problem is that that during the modeset the driver tries to disable the already disabled DP port. One solution would be to leave the port enabled during the unplug event handling and only disable it during the subsequent modeset. The attach patch does this, could you try it?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>