<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 --- - GPU crash dump"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78000">78000</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>GPU crash dump
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Ingo.Saitz@stud.uni-hannover.de
</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>unspecified
</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=98072" name="attach_98072" title="GPU crash dump saved to /sys/class/drm/card0/error">attachment 98072</a> <a href="attachment.cgi?id=98072&action=edit" title="GPU crash dump saved to /sys/class/drm/card0/error">[details]</a></span>
GPU crash dump saved to /sys/class/drm/card0/error
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not
a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
i915: render error detected, EIR: 0x00000010
i915: page table error
i915: PGTBL_ER: 0x00010000
[drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
i915: render error detected, EIR: 0x00000010
i915: page table error
i915: PGTBL_ER: 0x00010000
After this bug GLX applications (e.g. glxgears) threw core dumps on startup,
after displaying an empty black window.
After applying the fence counting patch (<span class=""><a href="attachment.cgi?id=75820" name="attach_75820" title="Fix up fence counts">attachment 75820</a> <a href="attachment.cgi?id=75820&action=edit" title="Fix up fence counts">[details]</a></span> <a href='page.cgi?id=splinter.html&bug=78000&attachment=75820'>[review]</a> from
<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [uxa PNV] EDEADLCK: Characters and fonts overwriting and/or missing, bad rendering and frozen sections of windows on >2.20.18"
href="show_bug.cgi?id=59771">https://bugs.freedesktop.org/show_bug.cgi?id=59771</a> ), dri applications continue
to work, and the Xorg server process outputs a fence error almost on startup
("Fixing up fence counts; was -1, expected 0" - the patch only displays this
error once).
I don't know how to trigger the error, other than using 3d-accelerated programs
for some time.
Package versions (current debian unstable):
mesa 10.1.0-5
libdrm 2.4.52-1 + fence counting patch applied
xorg-xserver 2:1.15.1-1
linux-kernel 3.14.1 (own config)
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_I915_FBDEV=y
# CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set
# CONFIG_DRM_I915_UMS is not set</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>