insmod drm.ko debug=1
thank you !
Vladimir Dergachev
This is all the output from the drm module with debugging enabled:
http://www.visualtech.com/drm.txt.gz
Thank you !
By the looks of it the kernel buffer is overflowing with messages.
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.
Also, it might be interesting to see what happens when you make various
calls into NOPs - for example do things work better when you make texture
calls into NOPs ? We would not expect the correct output, of course.
best
Vladimir Dergachev
The logging starts with X launching, and ends with UnrealTournament
in a lockup. It's about 1.6 megs gzipped, and 54 megs ungzipped, so
there's a whole lot of data in there, most of it probably redundant...
I haven't had a chane yet to try Aapo's patch against radeon_cursor.c, but
I should have some time when I get home this afternoon.
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
