Bug 93715

Summary: [r600g] rendering issues with R600_DEBUG=nosb for all three 'raytrace' variants
Product: Mesa Reporter: Dieter Nützel <Dieter>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium    
Version: git   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: vsraytrace.png
fsraytrace.png
gsraytrace.png

Description Dieter Nützel 2016-01-14 17:24:02 UTC
Created attachment 121038 [details]
vsraytrace.png

It occurs with RV730 and NI/Turks XT.
I've set Hardware to 'All' cause both x86 (IA32) and x86-64 (AMD64) are broken.

'all three 'raytrace' variants' mean:

vsraytrace
fsraytrace
gsraytrace

Have a look at the attachments.
Comment 1 Dieter Nützel 2016-01-14 17:24:36 UTC
Created attachment 121039 [details]
fsraytrace.png
Comment 2 Dieter Nützel 2016-01-14 17:25:00 UTC
Created attachment 121040 [details]
gsraytrace.png
Comment 3 Dieter Nützel 2016-01-14 17:42:49 UTC
Does it have something to do with the yellow colour?
It is in all there variants in the below, right and yellow coloured sphere.
Comment 4 Gert Wollny 2017-06-22 17:20:12 UTC
For me it works correctly with current mesa-git and a 6870 HD (Barts).
Comment 5 Dieter Nützel 2017-06-26 23:55:42 UTC
Yes,

it works correctly with current mesa-git and a RX580 (Polaris 20), now.

Hello Gert,
will try with my old 6670 HD (Turks XT) when I find more time to switch it back in.

But good progress so far.
Comment 6 GitLab Migration User 2019-09-18 19:20:51 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/570.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.