On Friday 03 June 2005 00:25, Benjamin Herrenschmidt wrote: > > > > > > You guys seem to be getting closer... > > > When I had X + xfce4 + quake3 running (with this patch + > > > patch.drm-cmdbuf-more-pacifiers + patch.remove-userspace-pacifiers) X > > > locked up within 2 minutes. > > > However, X + quake3 (no window manager), I went thirty minutes before > > > my first problem. Quake3Arena crashed, and X quit. There was some > > > message on the terminal about radeon_wait and "IRQ 16". > > > > > > Here it is: > > > > radeonWaitIrq: drmRadeonIrqWait: -16 > > Have you tried David Airlie's or my latest DRM IRQ fixes ?
It is unlikely that the problem is related, especially when X locks up, too. If you see this message and X is continuing to run fine (i.e. no complete lockup), you should indeed consider looking at the IRQ code. However, if X locks up completely, the most likely reason for this message is simply that the R300 locks up before it encounters the IRQ EMIT command in the ring buffer. It just happens then that the DRI client waits for an IRQ instead of busy-looping for the chip to idle. So it is perfectly likely that this message appears even when the IRQ handling code is working fine. Nevertheless, testing that patch can't hurt. cu, Nicolai
pgp5KDqFMYqUZ.pgp
Description: PGP signature
