<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 - [nv50] HW state is not reset correctly when using a new GL context"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90363">90363</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[nv50] HW state is not reset correctly when using a new GL context
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</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/nouveau
</td>
</tr>
<tr>
<th>Assignee</th>
<td>nouveau@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>matteo.mystral@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>nouveau@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=115622" name="attach_115622" title="Hack">attachment 115622</a> <a href="attachment.cgi?id=115622&action=edit" title="Hack">[details]</a></span>
Hack
Hardware state is not reset correctly when a process makes use of a new GL
context, after it has used and then destroyed the previous one.
This manifests in a (still uncommitted,
<a href="https://www.winehq.org/pipermail/wine-patches/2015-April/138974.html">https://www.winehq.org/pipermail/wine-patches/2015-April/138974.html</a>) Wine test
which fails on nv50. Actually commenting out stream_test(), which makes use of
instanced draws with ARB_instanced_arrays, workarounds the issue.
A single process executes both tests, destroying and then recreating a GL
context in between. AFAIU specifically the per-instance enable flags are never
reset on the HW and that breaks the latter test.
I'm attaching a patch which "fixes" the issue for me but it's not the correct
approach.</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>
</ul>
</body>
</html>