Bug 89256

Summary: [radeonsi][CSGO] many rendering artifacts and more
Product: Mesa Reporter: Sylvain BERTRAND <sylvain.bertrand>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact: Default DRI bug account <dri-devel>
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: dmesg
xorg.0.log

Description Sylvain BERTRAND 2015-02-21 02:07:00 UTC
Got my hands on counter-strike Global Offensive.

I run an up-to-date fedora rawhide on x86_64 (3.20 kernel and mesa 10.5.0).

I get a lot of rendering artifacts, GPU lock ups (rare, on ring 0 and 5), VM read faults from the TC block (texture cache I guess) for some VMs...

The video settings are set to the minimum (in a 1920x1080 window)

My GPU is a R9 280X (TAHITI XT).
Comment 1 Sylvain BERTRAND 2015-02-21 02:07:43 UTC
Created attachment 113712 [details]
dmesg
Comment 2 Sylvain BERTRAND 2015-02-21 02:08:08 UTC
Created attachment 113713 [details]
xorg.0.log
Comment 3 Michel Dänzer 2015-02-23 07:00:53 UTC
Does it work better with current Mesa Git master? Specifically, this commit might help at least for the rendering artifacts:

http://cgit.freedesktop.org/mesa/mesa/commit/?id=7692704b144b2aa9a57767a43212ceb5aad6638a
Comment 4 Sylvain BERTRAND 2015-02-23 19:54:40 UTC
Sorry, cannot build easily mesa git on fedora rawhide for x86_64 and x86. Some
dark kludge related to llvm blocked it (got some troubles with some "python
mako" stuff too). I would need to build manually a near whole devel graphic stack on
the side with all SDK dependencies.

Have to wait for fedora to sort out their kludgy kludge llvm mess or pray for a
fedora recent mesa update with the above patch.

Leave that bug be. Once I have a reasonable way to test mesa git, I'll come
back. (hope the fedora guys will provide a mesa update before me finishing my
distro).

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.