<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - System "forgets" about its DVI output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90804">90804</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>System "forgets" about its DVI output
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>steve@sk2.org
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=116214" name="attach_116214" title="Xorg.log">attachment 116214</a> <a href="attachment.cgi?id=116214&action=edit" title="Xorg.log">[details]</a></span>
Xorg.log
Hi,
My system regularly forgets about the screen connected to its DVI output, with
slightly varying symptoms. This used to happen irregularly, but since upgrading
to 1.17.1 (as packaged in Debian, 2:1.17.1-2) it's systematic. Even with no
power manager (I uninstalled xfce4-power-manager) and no screensaver, the
screen ends up going into powersave mode and X never comes back. Sometimes
switching to a text VT brings the screen back, and then restarting X works; but
often switching to another VT doesn't change anything, nor does restarting X;
only rebooting helps then.
I'm attaching Xorg.log, the kernel log, and working and failed watermarks and
register dumps. The latter reveals that the DVI output is just gone as far as
the system is concerned... I've tried disconnecting and reconnecting the DVI
cable, and that doesn't help either.
I've noticed lots of traces like
Jun 1 21:03:54 heffalump kernel: [52160.398608] [drm:drm_edid_block_valid]
*ERROR* EDID checksum is invalid, remainder is 215
Jun 1 21:03:54 heffalump kernel: [52160.398611] Raw EDID:
Jun 1 21:03:54 heffalump kernel: [52160.398612] 00 ff ff ff ff ff ff 00
22 f0 f7 26 01 01 01 01
Jun 1 21:03:54 heffalump kernel: [52160.398613] 25 12 01 03 80 36 23 78
ee ce 50 a3 54 4c 99 26
Jun 1 21:03:54 heffalump kernel: [52160.398614] 0f 5f ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
Jun 1 21:03:54 heffalump kernel: [52160.398615] ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
Jun 1 21:03:54 heffalump kernel: [52160.398616] ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
Jun 1 21:03:54 heffalump kernel: [52160.398617] ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
Jun 1 21:03:54 heffalump kernel: [52160.398618] ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
Jun 1 21:03:54 heffalump kernel: [52160.398619] ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff
with varying values; I don't know if that's relevant at all.
Regards,
Stephen</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>