On Friday 25 March 2005 06:08 pm, Jung-uk Kim wrote: > On Thursday 17 March 2005 01:02 pm, Jung-uk Kim wrote: > > On Thursday 17 March 2005 07:33 am, Jerome Glisse wrote: > > > > I rebuilt Xorg from CVS. It's actually ran glxgears this > > > > time! However in few seconds it just locked up OS (i. e., > > > > infinitely looping syscalls -> 100% CPU load). Another > > > > interesting thing is the gears are twice bigger than normal > > > > size and it looks interlaced. r300_demo shows the same > > > > symptom. Any thought? > > > > > > There are issue with mouse try to run glxgears and don't do > > > anymouse movement, it shouldn't lock, if it locks this likely > > > due to others issues. > > > > I was wrong about 100% CPU load. In fact, it was almost 100% > > idle. I can move mouse but I cannot type. I see ~50 IRQs per > > second from drm. When I tries to kill Xorg, then CPU load goes > > up 100%. Funny thing is I waited about 5 minutes (while copying > > the debugging output), gears started turning again! > > > > I set RADEON_DEBUG=all and the last lines before few minute pause > > were: > > > > r300ResetHwState > > r300Flush > > r300FlushCmdBufLocked from r300Flush - 1 cliprects > > Syncing in r300FlushCmdBufLocked (from r300Flush) > > > > r300Enable( GL_DEPTH_TEST = GL_TRUE ) > > r300Enable( GL_STENCIL_TEST = GL_FALSE ) > > Enabling VB->ObjPtr > > Enabling VB->ColorPtr[0] > > RR[0] - sz=4, reg-0, fmt=1 -- st=4, of=0x00000000 > > RR[0] - sz=4, reg-1, fmt=3 -- st=4, of=0x00000000 > > > > > Could you grab a screenshot of the interlaced effects ? > > > > I backed up my previous /usr/X11R6 directory and installed Xorg > > from CVS, so I cannot make glxgears' screenshot. The attachment > > is from r300_demo instead but you'll see what I mean. > > I have no idea who fixed it but I am able to run glxgears and > tuxracer reliably now! glxgears yields ~840FPS on FreeBSD/amd64 > 6-CURRENT. It's slower than expected but that's a start. ;-) > > FYI, everything's checked out from CVS today, i. e., FreeBSD, r300, > Xorg, and Mesa...
Wait, I have one thing that's not from CVS. I patched system compiler from GCC 3.4.2 to GCC 3.4.4 snapshot (20050318). I updated GCC because I found some nasty optimization bugs for AMD64 in GCC 3.4.2. Can this be the fix? Thanks, Jung-uk Kim > Cheers, > > Jung-uk Kim > > > Thanks, > > > > Jung-uk Kim > > > > > Jerome Glisse ------------------------------------------------------- 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
