<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Frequent loss of screen content, system barely usable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76608">76608</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Frequent loss of screen content, system barely usable
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>richih.mailinglist@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=96389" name="attach_96389" title="Content of /sys/class/drm/card0/error">attachment 96389</a> <a href="attachment.cgi?id=96389&action=edit" title="Content of /sys/class/drm/card0/error">[details]</a></span>
Content of /sys/class/drm/card0/error
System is barely usable. I am losing part, or all, of my GUI all the time.
A crash as below will eat all keyboard inputs and only allow ctrl-alt-f1 and
the like.
As per dmesg:
[ 2207.681554] [drm] stuck on render ring
[ 2207.681558] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2207.681558] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2207.681559] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2207.681560] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2207.681560] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2207.684342] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
(0xedf7000 ctx 1) at 0xedf7514
[ 2213.676422] [drm] stuck on render ring
[ 2213.676485] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
(0xfe61000 ctx 1) at 0xfe61214
[ 2213.676487] [drm:i915_context_is_banned] *ERROR* context hanging too fast,
declaring banned!
richih@eudyptes ~ % dpkg -l | grep linux-image | grep '^ii'
ii linux-image-3.13-1-amd64 3.13.6-1 amd64
Linux 3.13 for 64-bit PCs
ii linux-image-amd64 3.13+56 amd64
Linux for 64-bit PCs (meta-package)
richih@eudyptes ~ % uname -a
Linux eudyptes 3.13-1-amd64 #1 SMP Debian 3.13.6-1 (2014-03-19) x86_64
GNU/Linux
richih@eudyptes ~ %</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>