<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 - Reproducible GPU hang on Intel HD5500 — ecode 8:0:0x84df3c1c"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92623">92623</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Reproducible GPU hang on Intel HD5500 — ecode 8:0:0x84df3c1c
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (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>delroth@gmail.com
</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=119120" name="attach_119120" title="Xorg configuration used for headless tests">attachment 119120</a> <a href="attachment.cgi?id=119120&action=edit" title="Xorg configuration used for headless tests">[details]</a></span>
Xorg configuration used for headless tests
[root@duke ~]# pacman -Q mesa linux xorg-server libdrm
mesa 11.0.3-1
linux 4.2.3-1
xorg-server 1.17.2-4
libdrm 2.4.65-1
I was setting up an Intel NUC to run dolphin-emu.org graphical regression tests
(<a href="https://fifoci.dolphin-emu.org/">https://fifoci.dolphin-emu.org/</a>). The setup is simple: "headless" Xorg
(xorg.conf attached) and dolphin-emu running in that DISPLAY rendering tests.
Two of our tests consistently end up segfaulting on Intel GPUs with the
following log:
intel_do_flush_locked failed: Input/output error
Accompanied by the following in dmesg:
[ 215.432142] [drm] stuck on render ring
[ 215.433001] [drm] GPU HANG: ecode 8:0:0x84df3c1c, in FIFO-GPU thread
[394], reason: Ring hung, action: reset
[ 215.433003] [drm] GPU hangs can indicate a bug anywhere in the entire
gfx stack, including userspace.
[ 215.433004] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 215.433005] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 215.433006] [drm] The gpu crash dump is required to analyze gpu hangs,
so please always attach it.
[ 215.433007] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 215.435124] drm/i915: Resetting chip after gpu hang
[ 221.455258] [drm] stuck on render ring
[ 221.456246] [drm] GPU HANG: ecode 8:0:0x84df3c1c, in FIFO-GPU thread
[394], reason: Ring hung, action: reset
[ 221.458382] drm/i915: Resetting chip after gpu hang
The issue happens consistently when running these tests here. Unfortunately an
apitrace does not reproduce the problem, so here are some slightly involved
repro instructions using our software:
$ git clone <a href="https://github.com/dolphin-emu/dolphin">https://github.com/dolphin-emu/dolphin</a>
$ cd dolphin && mkdir build && cd build
$ cmake -DDISABLE_WX=ON ..
$ make -j4
$ rm -rf ~/.dolphin-emu
$ mkdir -p ~/.dolphin-emu/Config
$ wget
<a href="https://github.com/dolphin-emu/fifoci/blob/master/runner/linux/Config-ogl/Dolphin.ini">https://github.com/dolphin-emu/fifoci/blob/master/runner/linux/Config-ogl/Dolphin.ini</a>
-O ~/.dolphin-emu/Config/Dolphin.ini
$ wget
<a href="https://github.com/dolphin-emu/fifoci/blob/master/runner/linux/Config-ogl/gfx_opengl.ini">https://github.com/dolphin-emu/fifoci/blob/master/runner/linux/Config-ogl/gfx_opengl.ini</a>
-O ~/.dolphin-emu/Config/gfx_opengl.ini
$ wget
<a href="https://fifoci.dolphin-emu.org/media/dff/MarioSuperSluggersStarBar.dff">https://fifoci.dolphin-emu.org/media/dff/MarioSuperSluggersStarBar.dff</a>
$ Binaries/dolphin-emu-nogui -e MarioSuperSluggersStarBar.dff # <-
consistently crashes
I couldn't reproduce the same issue on an Haswell Intel HD chip, but that's
with slightly different software versions too.</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>