From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 90363] New: [nv50] HW state is not reset correctly when using a new GL context Date: Thu, 07 May 2015 16:46:53 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0622453658==" Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0622453658== Content-Type: multipart/alternative; boundary="1431017213.1BEd3600.14869"; charset="UTF-8" --1431017213.1BEd3600.14869 Date: Thu, 7 May 2015 16:46:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Reporter: matteo.mystral-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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. --1431017213.1BEd3600.14869 Date: Thu, 7 May 2015 16:46:53 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
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@lists.freedesktop.org
Reporter matteo.mystral@gmail.com
QA Contact nouveau@lists.freedesktop.org 

Created attachment 115622 [details]
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.
--1431017213.1BEd3600.14869-- --===============0622453658== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cDovL2xpc3RzLmZy ZWVkZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL25vdXZlYXUK --===============0622453658==--