<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#c19">Comment # 19</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:dev@blackamp.de" title="Daniel Michalik <dev@blackamp.de>"> Daniel Michalik</a> <pre>Chris Wilson wrote: > 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. Understood. Maybe that could be fixed to avoid confusion? > The interesting thing about the log you pasted is that it dies on a > modesetting operation. Ok, so nothing to do with the /sys/class/drm/*/status queries then. I need a few pointers to provide more information: > I guess drm.debug=6 dmesg would be relevant as well. What do you mean by 'drm.debug=6 dmesg'? Do I need to change dmesg settings in some way (how)? I can access dmesg of a (future) crashed session through /var/log/dmesg.1, but I don't know how to change the debug level that is written into this file. > Another problem is that you are using Present, What is 'Present'? > which is broken across screen resizes. How so, where can I read more? > You could try compiling the ddx with --disable-dri3 to see if that > helps at all. Ok. Let's try to get you more information first. > But I think dmesg is the next step towards working out the > cause of the freeze. I'll be happy to. Could you please point me at how to do that?</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>