On Mon, 2005-18-04 at 14:45 +0200, Geller Sandor wrote: > On Sat, 16 Apr 2005, khaqq wrote: > > > I had lockups a few months ago with my FireGL8800 with X/DRI, I gave up > > trying > > to find a stable X/DRI combination after trying 3 X versions and about 20 > > DRI > > snapshots. I'm *not* saying DRI isn't good, it used to work perfectly on my > > 7500. > > But the R200 was never stable here (I've had it for ~6 months now). > > I have to agree with you. I complained about the r200 driver some months > ago. I was told to try to track down the time when the instability of the > r200 driver started (some develorers suggested the end of > September, 2004).Unfortunately, I wasn't able to compile older CVS > snapshots on my debian sid system. It's very strange, I don't think that > X.org CVS was broken for months... (I tried compiling snapshots from > 2004.08.31 to 2004.11.30 without any success...)
Did you post the problems you encountered? > > I'm using ATI-drivers atm and I've not seen a single crash with those. If > > debug logs are > > interesting to you, or to any X/DRI developpers, I'll go back to DRI and > > try to > > generate them if you tell me how. I'm happy to say my PC doesn't seem to > > have > > any hardware problem (as it was suggested on dri-devel) since going to > > ati-drivers > > solved *all* the stability issues I had with X+DRI (and before switching > > from > > the 7500 to the 8800, it was stable ; and it was still stable in 3D apps in > > windows > > (yuck) after the switch). > > Maybe if all users seeing crashes generated a debug log and put it online > > for all DRI > > developpers to see, finding a common denominator would be easier... > > I use Descent3 for testing. With recent snapshots it's getting harder to > crash the game. Some months ago a simple X restart was enough to crash > Descent3 (and of course the X server) in a few seconds. Define 'a simple X restart'. Do you mean running Descent 3 right after restarting the X server? > Nowadays I have to switch to the microwave gun and fire some dozen waves > to crash X. It's 100% reproducible, so I offered my help to create gdb > backtraces, but one of the DRI developers (Michael Daenzer, if I remember > correctly) pointed out that gdb backtraces won't help diagnosing GPU lockups. Yeah, but maybe he was thinking of DRM debugging output or something. That can be useful, but is still tedious to wade through in the best case. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- 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_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
