Yes, I know 3D acceleration for R6xx/R7xx is very experimental. It's not my complaining here, just wanted to document my problems to help development. I use following stuff: http://cgit.freedesktop.org/mesa/mesa/log/?h=r6xx-r7xx-support commit cccd7ae6e60c2454f9b68e03ec561e9b780a065c R6xx: Fix memory free issue and correct clip rectangle http://cgit.freedesktop.org/~agd5f/drm/?h=r6xx-r7xx-3d commit dec0572d6e7e2ce1c6de2315a790e8de37c589c0 Fix typo in IT_EVENT_WRITE packet checker My problem is that about 3 seconds after calling glxgears my machine (GPU?) locks up. And I don't get even 1 frame rendered in that seconds. After lock up I can't switch to VT, can't use CTRL+ALT+BACKSPACE, can only reboot with SysRq. I logged on machine to get some logs. First I got top of "top": PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2581 root 20 0 672m 21m 6736 R 91 0.5 3:21.23 Xorg Then checked dmesg, it's full (hundreds) of: [drm] wait for fifo failed status : 0xA27334E0 0x00000103 [drm] wait for fifo failed status : 0xA27334E0 0x00000103 [drm] wait for fifo failed status : 0xA27334E0 0x00000103 On photo you can see part of output form starting glxgears. I started glxgears in screen, so after sshing I attached to screen and got full output. Hope it will help in developing Mesa driver :)
Created attachment 25053 [details] Photo of locked up screen.
Created attachment 25054 [details] Full output of glxgears. On photo output of glxgears is not full. It misses beginning and display locked up before last 4 lines you can see in attached log.
Created attachment 25055 [details] Xorg.0.log Nothing special here I think, you can see my card is: ATI Mobility 34xx, M82, RV620.
That bug was only in r6xx-r7xx-support branch, r6xx-rewrite branch was working fine and now master is as well.
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.