Bug 103397

Summary: [regression, bisected] broken geometry in almost every game
Product: Mesa Reporter: almos <aaalmosss>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: VERIFIED FIXED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description almos 2017-10-21 21:51:23 UTC 
2f4705afde707e8eb41b9414c25df91aa1ea2fb3 is the first bad commit
commit 2f4705afde707e8eb41b9414c25df91aa1ea2fb3
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Sun Oct 8 03:44:07 2017 +0200

    radeonsi: if there's just const buffer 0, set it in place of CONST/SSBO pointer


This change broke a lot of things on my Pitcairn GPU.

In KOTOR (with Wine) the character animations are broken. In Doom 3 and Quake Wars the whole geometry is broken. In Cogs the shadows are wrong and the menu screens are broken. In Furmark the background is fully green. In Unigine Valley I only see blackness, but Heaven is unaffected. Saints Row 2, Shadow Warrior, and Witcher 2 are unaffected.

D3D in Wine is curious: Portal 2, Just Cause, Crysis 2 are broken with wined3d but they're fine with nine, Stalker is fine with both wined3d and nine, Deus Ex Invisible War is broken with both. Portal 2 is also broken when running natively.

I've also tested games that use fixed-function rendering, those are unaffected.
(I've also realized that I have too many games installed)
Comment 1 Christoph Haag 2017-10-22 07:07:30 UTC 
Bug 103389 bisected to the same commit.
Comment 2 Marek Olšák 2017-10-27 11:08:41 UTC 
Fixed with https://cgit.freedesktop.org/mesa/mesa/commit/?id=3f8e3c2bd8f54ae6817f7496be47f4e1a8860d9c

You also need to update LLVM 6.0 from git or switch to LLVM 5.0. Anything in between will lead to the same corruption.
Comment 3 almos 2017-10-27 23:36:32 UTC 
With llvm 5.0 and mesa master everything is fine. Thanks.

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.