[Nouveau] [Bug 90363] New: [nv50] HW state is not reset correctly when using a new GL context

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90363

            Bug ID: 90363
           Summary: [nv50] HW state is not reset correctly when using a
                    new GL context
           Product: Mesa
           Version: git
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: matteo.mystral at gmail.com
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 115622
  --> https://bugs.freedesktop.org/attachment.cgi?id=115622&action=edit
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,
https://www.winehq.org/pipermail/wine-patches/2015-April/138974.html) 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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20150507/b824cf0d/attachment-0001.html>