On Fri, 18 Feb 2005, Nicolai Haehnle wrote:
Hi everybody,
As reported earlier, I had a perfectly repeatable lockup in VB mode that always happened after the exact same number of frames in glxgears. I can't explain everything about the lockup, mostly because I still don't know what the two registers in the begin3d/end3d sequence actually mean, but here's what I know:
It turns out that after the first 4 DMA buffers had been used to completion, r300FlushCmdBuf() was called from r300RefillCurrentDmaRegion(). This only caused simple state setting commands as well as an upload of the current vertex program into the VAP. There was no rendering going on, and neither the begin3d nor the end3d sequence was part of the commands that were sent to the card. However for some reason, it was this sequence that caused the lockup.
Great !
Unfortunately, VB mode still locks up for me. (I did update to the very latest CVS and made sure there were no other changes).
There could two "obvious" causes:
1. we do not emit sync_VAP() sequence after programming VAP registers
2. I am using MergedFB mode and in that case the cursor movement triggers an INREG() from RADEON_CRTC2_GEN_CNTL and RADEON_CRTC_GEN_CNTL.
I would not expect INREG from these registers to cause immediate lockups,
but if I comment it out the lockups do not occur as often (but when they do they are still hard).
Any ideas ?
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 Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
