I have played a bit trying to find out the cause of the vb mode lockups.
First of all I doubt this is due to overheating - I get a lockup the moment I move my mouse on the konsole. This is unlikely to add extra load to the GPU.
Secondly, I tried commenting out RADEONChooseCursorCRTC function in ati/radeon_mergedfb.c (this is part of 2d driver within X.org CVS).
(Strictly speaking I did not comment out the entire function but rather caused it to run exactly once - so it is not run when a 3d app is started).
This change significantly reduced the probability of the lockups - I could not get glxgears to lockup at all, but Quake locked up eagerly when I crossed window boundary.
The interesting part about this function is that it does INREG() in order to do masked write - everything else that touches cursor is ok.
Conclusions:
* this is unlikely to be a heat related issue
* it could be that R300 hardware is more sensitive to register
access for cursor related registers - though I do not think
this is likely as I saw cursor move freely during soft lockup * more likely is that there is an error someplace (like command
buffer being split or something) and mouse movement triggers
it (perhaps by inserting a delay)best
Vladimir Dergachev
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
