Hi, this is my first bug report, so feel free to point me in a different direction if necessary please. I am getting a flawless 30+ fps on one of the tutorial maps without any graphical glitch. However on a different map, there are heavy texture issues. Please see: http://youtu.be/wHLVaa5aTmA Last few lines from dmesg after gameplay: [ 3375.201258] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 3375.223619] radeon 0000:02:00.0: evergreen_cs_track_check:974 mask 0x00000777 | 0x00000FFF no cb for 2 [ 3375.223625] radeon 0000:02:00.0: evergreen_packet3_check:1918 invalid cmd stream [ 3375.223628] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 3375.248243] radeon 0000:02:00.0: evergreen_cs_track_check:974 mask 0x00000777 | 0x00000FFF no cb for 2 [ 3375.248254] radeon 0000:02:00.0: evergreen_packet3_check:1918 invalid cmd stream [ 3375.248259] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! Setup details: Game: Dota 2 Game version: latest update on January 9, 2014 Settings: Highest settings on 1920x1080 (low shadows) Kernel: 3.13.0-031300-generic GPU: 6550M GPU RAM: 1GB DDR3 CPU: i3 380m 2.5GHz RAM: 8GB DDR3 Distribution: Ubuntu 13.10 OpenGL version string: 3.0 Mesa 10.1.0-devel (git-d6b6ab5 saucy-oibaf-ppa+curaga) Thank you, Matyas
I am happy to do additional digging if someone points me in some direction.
Possibly related to bug 68451.
I tried running Dota2 with R600_DEBUG=noinvalrange %command% -console R600_DEBUG=noinvalrange,nodma,nocpdma %command% -console R600_DEBUG=nodma,nocpdma %command% -console ...neither helps. I don't understand why 68451 has been marked as fixed though. I'll retry this weekend with 3.14rc2, unless someone advises on what next to try out.
I've compiled the latest kernel from GIT (3.14), and the texture corruption is gone.
(In reply to comment #3) > I tried running Dota2 with > R600_DEBUG=noinvalrange %command% -console > R600_DEBUG=noinvalrange,nodma,nocpdma %command% -console > R600_DEBUG=nodma,nocpdma %command% -console > > ...neither helps. I don't understand why 68451 has been marked as fixed > though. I'll retry this weekend with 3.14rc2, unless someone advises on what > next to try out. See comment 48 in bug 68451 for an explanation about why it was marked as fixed. In short, the original bug (identified problematic commit on given hardware) has been fixed. The other reports must be treated as different bugs.
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.