From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 [thread overview]
Message-ID: <bug-90363-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2968 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-05-07 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 16:46 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-90363-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-05-07 16:51 ` [Bug 90363] [nv50] HW state is not reset correctly when using a new GL context bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-07 18:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-07 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-09 17:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-90363-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.