as before 2D is working just fine. 3D. when I run gears for some time eventually it hangs. Now it seems that the gears starts to use 99.9% of CPU time instead of the X. So I compiled gears with -g and ran it remotely from gdb. so here's what I got. . . 2966 frames in 5.001 seconds = 593.081 FPS Program received signal SIGINT, Interrupt. delay () at radeon_ioctl.c:378 378 } (gdb) bt #0 delay () at radeon_ioctl.c:378 #1 0x404ff566 in radeonWaitForFrameCompletion (rmesa=0x80761d0) at radeon_ioctl.c:403 #2 0x404ff6a4 in radeonSwapBuffers () at radeon_ioctl.c:408 #3 0x4051902f in XMesaSwapBuffers () at radeon_xmesa.c:98 #4 0x403d617c in driMesaSwapBuffers (dpy=0x804b698, drawPrivate=0x804d770) at dri_mesa.c:628 #5 0x40108fa9 in glXSwapBuffers () at glxcmds.c:481 #6 0x40034da3 in glutSwapBuffers () at glut_swap.c:46 #7 0x8049cf1 in draw ()warning: find_solib: Can't read pathname for load map: Input/output error Cannot access memory at address 0x80000002. (gdb) would this help anyone? this seems quite the same I had previsously which I debugged with kdb in kernel. there is radeonWaitForFrameCompletion (rmesa=0x80761d0) at radeon_ioctl.c:402 402 for ( i = 0 ; i < 1024 ; i++ ) { 403 delay(); until i==1024 395 frame = INREG( RADEON_LAST_FRAME_REG ); 397 if ( sarea->last_frame - frame <= RADEON_MAX_OUTSTANDING ) { 402 for ( i = 0 ; i < 1024 ; i++ ) { 403 delay(); <back to up> And this goes on indefinately as before. sooooou any hints as what might cause this? -- Janne echo [EMAIL PROTECTED] | tr acefhiklnptu utpnlkihfeca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel