[Bug 84718] DP MST: re-docking messes up displays

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=84718

--- Comment #19 from Daniel Michalik <dev at blackamp.de> ---
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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141009/743421bf/attachment.html>