Hi there, this is a update of bug #31046, where the main issue was GPU resets caused by enabling tiling (R600_FORCE_TILING=1) with the r600g driver. The situation however was changed, and now R600_FORCE_TILING only causes mipmap rendering errors in a few application. Last time I tested ioquake3, doom3 (demo) and both ut2003 and ut2004. ut03 and ut04 are still affected by the blocky rendering errors (see the other bug for screenshots illustrating the problem), but both ioquake3 and doom3 now look perfectly fine. My hardware: ATI Technologies Inc Radeon HD 4770 [RV740] libdrm, mesa and xf86-video-ati are all git master tip. ColorTiling is enabled in the xorg.conf, verified this by checking the Xorg logfile. kernel is d-r-t Greets, Tobias
Can no longer reproduce this issue. So it looks fixed.
It's still there. Tiling is just disabled by default and the environment variable changed to R600_TILING. Just try the piglit test fbo-generatemipmap-formats with: R600_TILING=on piglit/bin/fbo-generatemipmap-formats and switch to NPOT textures with 'd' and go through various test sets ('n'). Some of them are still rendered wrong.
Yeah, you're right -- I completly forgot that the envvar changed :(
Retested with the correct envvar and I still can't reproduce the artifacts. They don't appear anymore in ut2003 and ut2004, which were the only remaining games on my list. Leaving this open, since Droste still seems to have issues (I didn't check these tests).
Could you test nexuiz (just to check that it's not my fault in some way)? It should be visible there too. I can't test ut2k3/2k4.
No, also no errors visible there. Which kernel do you use? Using the drm-next branch here.
Currently I'm running drm-fixes (built ~1h ago). Most probably it's only visible on some cards (evergreen/juniper here). (libdrm, mesa and ddx were also updated to current git master ~1h ago)
I'm closing this one then, since it was primarly about the R700 series and the artifacts I experienced in games using the ut engine.
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.