Nicolai Haehnle wrote:
It is easy to blame the DDX, but the truth is, we just don't know. The
people seeing lockups should try to figure out whether there is a direct
causal connection between e.g. mouse movements and lockups. If you are in a
fullscreen OpenGL applications, not moving the mouse, no popups occuring
from something like a panel applet, and the chip *still* locks up, it is
highly unlikely that the DDX is at fault.
How about if you're in a window, no mouse movement, no popups,
running the Q3A demo level three times in a row followed by the
UTBench demo twice, and there are no lockups? Does that tell you
anything?
Vladimir Dergachev wrote:
In the past I found useful not to turn drm debugging on, but, rather,
insert printk statements in various place in radeon code. This should
also provide more information about what is actually going on.
I can't make any promises. My partner already thinks I spend too much
time in front of the computer :-) I'll see what I can do, though. Think a
printk statement at the start and end of every function? Have any
suggestions about what files to start with? Is there some consensus that
this is probably a cursor problem now?
Adam
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
