<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 - [ICL] GPU hangs in TerrainFlyTess with Iris"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111936">111936</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[ICL] GPU hangs in TerrainFlyTess with Iris
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI 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>not set
</td>
</tr>
<tr>
<th>Priority</th>
<td>not set
</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>eero.t.tamminen@intel.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=145683" name="attach_145683" title="TerrainFlyTess ICL error state">attachment 145683</a> <a href="attachment.cgi?id=145683&action=edit" title="TerrainFlyTess ICL error state">[details]</a></span>
TerrainFlyTess ICL error state
Setup:
* HW: ICL-U D1
* OS: Ubuntu 18.04 with Unity desktop (compiz)
* SW: git versions of drm-tip 5.4-rc2 kernel, X server & Mesa
* Desktop uses i965, benchmarks use Iris
Use-case:
* Run SynMark TerrainFlyTess with Iris:
MESA_LOADER_DRIVER_OVERRIDE=iris ./synmark2 OglTerrainFlyTess
Expected outcome:
* Like on GEN9, no GPU hangs
Actual outcome:
* Recoverable GPU hangs, see attachment
* Reproducibility: always
Notes:
* This test-case tests CPU<->GPU synchronization, by generating the terrain
data on-fly in 4 CPU threads with AVX, for GPU tessellation & rendering
* No idea whether these hangs are an regression. It seems to have happened
already >2 weeks ago on drm-tip v5.3 when I first did ICL testing
Kenneth from Mesa team already looked at the error state and commented that:
"This error state makes no sense, ACTHD points at the very start of the batch
and IPEHR is 0x18800101 which never appears in the error dump at all. Sounds
like a kernel bug to me."</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>