<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DP MST: re-docking messes up displays" href="https://bugs.freedesktop.org/show_bug.cgi?id=84718#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DP MST: re-docking messes up displays" href="https://bugs.freedesktop.org/show_bug.cgi?id=84718">bug 84718</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Daniel Michalik from <a href="show_bug.cgi?id=84718#c17">comment #17</a>) > Another thing I still haven't understood. Upon undocking, DP-3, DP-4, and > DP-5 get removed according to the log. Upon re-docking they get removed > again, according to the log. Two comments: > a) They shouldn't exist when re-docking? > b) They should be added, not removed when re-docking? It's just a bad log message. It's in the core Xorg code to handle hotplugging of whole GPU devices and responds to any drm hotplug event and prints confusing log messages. The interesting thing about the log you pasted is that it dies on a modesetting operation. I guess drm.debug=6 dmesg would be relevant as well. Another problem is that you are using Present, which is broken across screen resizes. You could try compiling the ddx with --disable-dri3 to see if that helps at all. But I think dmesg is the next step towards working out the cause of the freeze.</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>