<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [gm45] display is black or 1 solid color (white, etc), xrandr reset fixes temporarily"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78462#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [gm45] display is black or 1 solid color (white, etc), xrandr reset fixes temporarily"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78462">bug 78462</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>That the screen spontaneously dies would suggest a FIFO or SR underrun. I don't
think the great WM updates touched g4x per-se, but it is always worth checking
drm-intel-next in case they did magically fix something. You should also
disable output polling (use drm_kms_helper.poll=0). Also running with
drm.debug=6 and note the time when the screen dies so that we can see if there
is any event about that time.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>