I am using DRI2/KMS with the latest drm-next from airlied .. and mesa from git aswell.. ATI Technologies Inc RV770 [Radeon HD 4870] To reproduce: When loading a level in nexuiz it hangs completely while X is using 100% cpu.. I can kill X, but it will not be able to start again I think, or rather it just shows garbage after this. From bisecting I found that: commit 44c6c20b69839ea130a255496f5f692186b68793 Author: Andre Maasikas <amaasikas@gmail.com> Date: Fri Oct 9 10:46:12 2009 +0300 r600: fixup KIL instruction a bit - KILLGT takes 2 arguments - arb KIL has no dst register - add TODO about clause ending but currently piglit fp-kil passes and does not hang the card was the culprit.. reverting it makes it work for me.. Any more information needed?
I cant reproduce that, any specific level I need to load? have you modified any graphics settings? I dont think the game uses kill at all, I'v even tried an assert in that function which is the only one modified by that patch and it is never hit.
What versions of nexuiz? Maybe some of the code has changed. Also, maybe try and 'make clean' in your mesa tree and re-install.
nexuiz 2.5.2 sometimes it even locks up in the menus .. I use an ebuild which downloads from git, and after it has made a working copy of the repository I revert the mentioned commit.. I will now put in an assert myself there to see if it triggers instead of reverting the patch and verify that it actually impacts it directly .. Going to put it into the top of assemble_KIL() right? :)
Very strange I seem unable to reproduce it right now with newest mesa, but was able to reproduce it earlier very reliably, and could easily test if it worked .. but since then I have updated kernel, xorg-server and xf86-video-radeon ..
Hm, well nexuiz definitly makes it hang within 20 minutes, but it seems it is not connected to that commit at all now, atleast when it hangs I do not get any off the output I put in there.. only thing is that it seems to happen more often with that commit, but that could be a coincident .. drmRadeonCmdBuffer: -16. Kernel failed to parse or rejected command stream. See dmesg for more info. And in dmesg: [ 330.458381] [drm:radeon_ib_get] *ERROR* radeon: IB(2:0x0000000010121000:15872) [ 330.458384] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB [ 330.458386] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! So since it hangs, sometimes quicker than other times, and the correlation does not seem strong enough, maybe this bug should just be closed? I actually spent a lot of time to make sure that it was that commit that caused the difference before reporting a bug, and now I can't reproduce it. Sorry to waste your time like this..
I get the same dmesg messages on my mobility 2400 (m72/rv610). See bug #24218
Upgraded my BIOS now, and after that I had no crashes since .. My mb is a gigabyte ma790fxt-ud5p, the bios version was f3(k or m) and upgraded it to f7, for some reason this helped.. can't say for sure though... Closing this as NOTOURBUG as it is obviously not a fd.o BUG..
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.