Summary: | Regression with left for dead 2 | ||
---|---|---|---|
Product: | Mesa | Reporter: | kdj0c |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=88561 https://bugs.freedesktop.org/show_bug.cgi?id=90378 |
||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
kdj0c
2015-02-19 14:12:55 UTC
apitrace available at https://djinvi.net/jirafeau/f.php?h=1Gs0-v6H Did you try the patch form 88561 comment 6. I still see some glitches in your trace with that patch, although it may be worse without it (didn't test). Didn't get any GPU lockups or errors in dmesg with the trace, even after running it a couple of times. GPU: Radeon HD 7950 (OpenGL renderer string: Gallium 0.4 on AMD TAHITI) Mesa git-6c34fd2 + "radeonsi: don't use SQC_CACHES to flush ICACHE and KCACHE on SI" LLVM r229671 Kernel 3.19.0-gentoo the patch is now merged on upstream, so I just had to rebuild lib32mesa-git. also I had a build error due to commit, so I checkout a commit or two before: 41b1882ed45f0fcb827a178cb3f7143fcaa8c4d9 mesa: Use u_math.h from macros.h When replaying the trace, the glitches are still there, but when playing the game, most of the glitches are gone. (there are still a few, but I will need to take long apitrace to capture it). also gpu hang seems to be gone too. Are you still experiencing lockups? If so, can you a) run the game with R600_DEBUG=switch_on_eop and b) compile LLVM with the patch from bug #90378 comment 2 and run without R600_DEBUG This should at least confirm if we are seeing the same issue. kdj0c, Could you please give us feedback on the current state of this bug. Thanks. no more issue on Mesa 10.6.4. |
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.