<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 - GPU HANG: ecode 7:0:0x87d73c1a, in urbanterror [10986], reason: hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108358">108358</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 7:0:0x87d73c1a, in urbanterror [10986], reason: hang on rcs0, action: reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</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>holgersson@posteo.de
</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=142024" name="attach_142024" title="crash dump from /sys/class/drm/card0/error">attachment 142024</a> <a href="attachment.cgi?id=142024&action=edit" title="crash dump from /sys/class/drm/card0/error">[details]</a></span>
crash dump from /sys/class/drm/card0/error
Hi,
I ran the first person shooter urbanterror and got a hanging system for some
seconds. Afterwards I inspected the kernel ring buffer and found the following
in dmesg:
[ 8856.096653] [drm] GPU HANG: ecode 7:0:0x87d73c1a, in urbanterror [10986],
reason: hang on rcs0, action: reset
[ 8856.096655] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 8856.096656] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 8856.096657] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 8856.096658] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 8856.096659] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 8856.096705] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 8864.189283] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 8865.701281] sysrq: SysRq : Keyboard mode set to system default
[ 8872.085862] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 8880.189122] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 8888.082397] i915 0000:00:02.0: Resetting chip for hang on rcs0
The sysrq comes from my attempt to gain back control to switch to a TTY
and inspect the issue as I first thought it would have been OOM.
I'm running Gentoo with KDE Plasma 5 and xorg-server-1.20.1.
My kernel is 4.18.14 from upstream with some of the genkernel patches, but only
ones for additional menus, CPU detection (-march=native) and so on, but nothing
related to graphical components.
Please let me know if you need further details.</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>