<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 - [gen9] Hang recovery fails for atomic+textureBuffer hang"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110998">110998</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[gen9] Hang recovery fails for atomic+textureBuffer hang
</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>jason@jlekstrand.net
</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>In <a class="bz_bug_link
bz_status_NEW "
title="NEW - [cfl] GPU hang when running UE4Editor"
href="show_bug.cgi?id=110228">https://bugs.freedesktop.org/show_bug.cgi?id=110228</a> we have a reported bug
where the GPU hangs in certain L3$ atomic + textureBuffer cases. The fact that
it's hanging is most likely a userspace mesa bug. However, I have never seen a
system come back from this hang on any kernel I've tried it on in the last two
years. (The bug has only been open for 6 months but I've experienced the exact
same hang as far back as two years ago.) The fact that it's hard-hanging is
definitely a kernel bug.
Steps to reproduce:
1. Install any version of the Linux Vulkan driver (we've had this hang since
about forever so a moderately recent distro driver should work.)
2. Download reproducer_v2 from #110228
3. Build with cmake
4. Run ./cs_hang 512
5. Watch it burn
This hang is present on at least SKL, KBL, and CFL but probably also APL. It
is not present on BDW or ICL so it can't be tested there (though the recovery
path might still have a bug on those platforms).</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>