hello unfortunately your mail got "lost" somehow. In the meantime I searched bugs.xfree86.org and found bugs #787 and #788 which I think are related to this problem.
I added some info to bug #788. Later I noticed that "his" problem was on *BSD, not on Linux. Maybe you could have a look at it. http://bugs.xfree86.org/show_bug.cgi?id=788 Am 2003.11.22 23:29:47 +0100 schrieb(en) Michel D�nzer: [...] > You're saying there are UT2003 binaries for PPC? ;) hmmm ;) maybe not. sorry. [...] > > how to trigger the bug: > > start glxgears, start quake3 in windowed mode, > > You're saying... ;) ;) I found another program using scissors that triggers (maybe) the same bug: lesson24 from nehe.gamedev.net http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=24 (glut and sdl source) The difference is: when triggering the bug with q3a both gl-apps exit() with r200WaitIrq: drmRadeonIrqWait: -16 and the Xserver loops, no cursor-movement... when triggering the bug with lesson24, one program loops and gets #1 in top (99,x% CPU), and you have at least a moving cursor. After killing -KILL the programs, the Xserver becomes #1 -> now you have the same result you get with quake3. > > > go to the model choosing menu, fiddle around a bit, > > try different models, push the back/forw. buttons, > > choose another model... and somewhen it should happen: > > glxgears and quake3 exit with > > r200WaitIrq: drmRadeonIrqWait: -16r200WaitIrq: drmRadeonIrqWait: -16 > > Another symptom of a lockup: the awaited interrupts never arrive. > > I'm curious, does this only happen if the windows overlap, or > regardless? I dont know. Im going to try it out. [...] > > I guess the chip lockup turns into a full system lockup when trying to > (re-)initialise the chip or something. > > > Couldnt it be possible to somehow regenerate/reset the card? > > Dunno, suspect not. > maybe Hui Yu has some hints? At least the ati drivers for another os got a "reinitialise the chip gracefully" or something similar on the features/changes list sometime ago. > > > What needs to be defined in host.def to get better debug-info in the > > static build? (XFree86 CVS HEAD) > > What kind of information are you thinking of? I thought of linenumbers and variable names. Both are there when building from DRI CVS, but none of them is there when building XFREE86 CVS HEAD. best regards, Andreas ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
