Henry Worth wrote: > > > BTW, I do see quite a few "128(0): Idle timed out, resetting engine..." > being logged by r128_accel.c's R128WaitForIdle() routine when running > x11perf with both the old and new drivers.
Tripped a different hang running xine in agp mode with XV dma disabled. With xine running, started glxgears and X hung. Killed glxgears and kde appeared to be restarting the desktop and then xine stuttered a few times before X hung again. During this, the cpu monitor showed high system cycles and lots of the following messages where being logged by r128_accel.c's R128CCEGetBuffer: (EE) R128(0): R128CCEGetBuffer: CCE GetBuffer -1002 (EE) R128(0): GetBuffer timed out, resetting engine... And the kernel log has this a few thousand times: kernel: [drm:r128_freelist_get] *ERROR* returning NULL! I could kill X from a telnet session, but the screen wouldn't clear and the kybd didn't seem responsive, had to reboot. Introduced by the COMMIT_RING changes, an example of the sync problems, or a bit of both? I think I've seen a few of these messages in the past, but don't recall a flood of them. Henry ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
