<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 - [BYT] Unable to purge GPU memory due lock contention."
href="https://bugs.freedesktop.org/show_bug.cgi?id=99036">99036</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BYT] Unable to purge GPU memory due lock contention.
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>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>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mark.a.janes@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>BYT intermittently report the following dmesg error when executing piglit:
Unable to purge GPU memory due lock contention.
Subsequently, the machine fails other GPU test suites, and eventually
hard-hangs.
I've performed hundreds of piglit runs on byt to reproduce this intermittent
issue. The earliest I have seen it is:
029e8ff81c65c2e0562be4a5d93fe83a9df49233
radv: Initialize the shader_stats_dump flag.
It's likely that this is triggered by a i965 commit just prior to 029e8ff. I
will continue to test in an attempt to identify the regression more precisely.</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 the QA Contact for the bug.</li>
</ul>
</body>
</html>