Summary: | Clive Barker's Jericho displays strange,vivid colors when motion blur enabled | ||
---|---|---|---|
Product: | Mesa | Reporter: | Béla Gyebrószki <gyebro69> |
Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED FIXED | QA Contact: | Nouveau Project <nouveau> |
Severity: | normal | ||
Priority: | medium | CC: | gyebro69, imirkin |
Version: | 11.2 | Keywords: | bisected, regression |
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
screenshot
failing tgsi shader |
Description
Béla Gyebrószki
2016-06-17 17:53:45 UTC
The trace replays fine on my GF119. I guess it's a Kepler issue. Created attachment 124590 [details]
failing tgsi shader
Somehow the attached shader manages to generate
BB:11 (4 instructions) - idom = BB:8, df = { BB:5 }
-> BB:26 (tree)
-> BB:12 (tree)
45: mov u32 $r4 $r14 (8)
46: mov u32 $r5 $r15 (8)
47: tex 2D $r1 $s0 f32 $r4t $r4d (8)
48: set ftz u8 $p0 neu f32 $r7 neg $r7 (8)
BB:12 (4 instructions) - idom = BB:11, df = { BB:13 }
-> BB:13 (forward)
49: $p0 add ftz f32 $r17 $r17 $r4 (8)
50: $p0 add ftz f32 $r18 $r18 $r5 (8)
51: $p0 add ftz f32 $r19 $r19 $r6 (8)
52: $p0 add ftz f32 $r16 $r16 1.000000 (8)
Which is obviously missing a texbar. Investigating.
https://patchwork.freedesktop.org/patch/94103/ That fixes the trace for me. Technically the issue wasn't *caused* by that commit... the bad logic existed already. But the old logic didn't pick up the "uses" at the top of the loop, which in turn meant that it kept the uses after the tex. Oh well. (In reply to Ilia Mirkin from comment #4) > v2 here: > > https://patchwork.freedesktop.org/patch/94106/ The patch fixes the problem in the game, thank you. |
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.