Am 2003.11.19 23:15:15 +0100 schrieb(en) Michel Dänzer: > 'That' annoying hang? Have I missed something? *shrug*
maybe.. You will get something similar when running ut2003_demo in non-tcl mode, too. (on radeon7500 and on r200/radeon8500) [...] > > isnt it strange that RADEONWaitForIdleCP somehow calls fbBresDash32() ? > > I suspect that you've been chasing red herrings, my bet for the > mysterious symbol is on drmCommandNone(), which gets resolved by the > server's dynamic loader (or doesn't, when the DRI is disabled). Build a > static server to get reliable debugging info, but I doubt it'll help for > the actual problem: yes, in the static build it points to drmCommandNone(), but the hang still occurs. how to trigger the bug: start glxgears, start quake3 in windowed mode, 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: -16 > > killall -KILL X -> System hangs, no ping > > Sounds like a good old chip lockup. :\ > But why does the system still work until after KILLing the Xserver? Couldnt it be possible to somehow regenerate/reset the card? What needs to be defined in host.def to get better debug-info in the static build? (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
