From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 99532] New: Compute shader doesn't give right result
under some circumstances
Date: Wed, 25 Jan 2017 11:35:33 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1992522125=="
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
--===============1992522125==
Content-Type: multipart/alternative; boundary="14853441340.9c225D01.4587";
charset="UTF-8"
--14853441340.9c225D01.4587
Date: Wed, 25 Jan 2017 11:35:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D99532
Bug ID: 99532
Summary: Compute shader doesn't give right result under some
circumstances
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: stu_dby-KN7UnAbNpbg@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Created attachment 129135
--> https://bugs.freedesktop.org/attachment.cgi?id=3D129135&action=3Dedit
apitrace of my program
When I'm doing a course project in my compute graphics class, I found my
program didn't fully work on nouveau while it was working fine on intel and
nvidia proprietary drivers. It is a program using deferred shading with some
shadow map techniques, and it has an option to draw a "histogram" of depth
distribution sampled by a compute shader. I found histogram was showing wro=
ng
results (totally blank) on nouveau.
After looking into the problem for a while, I happened to find that if I di=
dn't
render the histogram (i.e. didn't use compute shader to sample) on the first
frame, the histogram would go wrong, otherwise, it would be okay.
This problem can be reproduced with the attached apitrace file, recorded wi=
th
simplified program and trimmed to contain only 4 frames. The first 2 frames=
are
mainly initialization and the third frame renders the scene from one angle
without generating histogram. The last frame renders the scene from another
angle and generates a histogram at bottom-right edge, which is completely b=
lank
on nouveau. However, if the trace is further trimmed to contain frame 0,1,3,
the histogram will render correctly. (Results of the two will be attached
below)
I'm willing provide assistance if needed.
--=20
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.=
--14853441340.9c225D01.4587
Date: Wed, 25 Jan 2017 11:35:34 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
| Bug ID |
99532
|
| Summary |
Compute shader doesn't give right result under some circumsta=
nces
|
| Product |
Mesa
|
| Version |
unspecified
|
| Hardware |
Other
|
| OS |
All
|
| Status |
NEW
|
| Severity |
normal
|
| Priority |
medium
|
| Component |
Drivers/DRI/nouveau
|
| Assignee |
nouveau@lists.freedesktop.org
|
| Reporter |
stu_dby@126.com
|
| QA Contact |
nouveau@lists.freedesktop.org
|
Created attachment 129135=
[details]
apitrace of my program
When I'm doing a course project in my compute graphics class, I found my
program didn't fully work on nouveau while it was working fine on intel and
nvidia proprietary drivers. It is a program using deferred shading with some
shadow map techniques, and it has an option to draw a "histogram"=
of depth
distribution sampled by a compute shader. I found histogram was showing wro=
ng
results (totally blank) on nouveau.
After looking into the problem for a while, I happened to find that if I di=
dn't
render the histogram (i.e. didn't use compute shader to sample) on the first
frame, the histogram would go wrong, otherwise, it would be okay.
This problem can be reproduced with the attached apitrace file, recorded wi=
th
simplified program and trimmed to contain only 4 frames. The first 2 frames=
are
mainly initialization and the third frame renders the scene from one angle
without generating histogram. The last frame renders the scene from another
angle and generates a histogram at bottom-right edge, which is completely b=
lank
on nouveau. However, if the trace is further trimmed to contain frame 0,1,3,
the histogram will render correctly. (Results of the two will be attached
below)
I'm willing provide assistance if needed.
You are receiving this mail because:
- You are the QA Contact for the bug.
- You are the assignee for the bug.
=
--14853441340.9c225D01.4587--
--===============1992522125==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt
YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m
cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg==
--===============1992522125==--