From: Adam K K. <ad...@vo...> - 2005-02-07 19:39:13
|
Roland Scheidegger wrote: > Geller Sandor wrote: > >>> I just removed the AGPFastWrite and DynamicClocks options. The crashes >>> still happen though. >> >> >> >> Looks like not only I have problems with the radeon driver. I update the >> X.org, drm, Mesa CVS once a week, but haven't found a working >> combination >> since 4-5 months... >> >> I don't intend to start a flame-war, but is there anybody who can use >> the >> r200 driver without X crashes? I'm testing X.org CVS regularly >> (almost on >> every weekend) with my RV280, with the latest linux 2.6 kernel. > > I suspect that quite the contrary, almost noone has crashes. This is > probably part of the problem, if they happen only for few people with > very specific configurations, none of the developers can reproduce it > and it will just remain unfixed. > For reference, I never get crashes with the r200 driver (on a rv250), > at least none which I can't directly reference to my own faults when > playing around with the driver... At least since the state submit > fixes half a year ago the driver seems quite solid for me. Except the > hard lockup I got for some very odd reason when I used a gart size of > 64MB, though that was on a r100. > > Roland > Agreed, for the most part. I use an 8500 and 9200 at work and at home. I regularly update my Mesa tree and build new version of the r200 driver. The only problems I've experienced is if I leave xscreensaver up and running all night, randomly choosing from the OpenGL screensavers... I'll sometimes (once a week, maybe) find X locked solid, and only a reboot will get it working again. The XiG drivers do this as well, the only difference being that I am able to just kill the GL screensavers that are locked up and get my display back :-) I think perhaps the biggest culprit for this problem with the Mesa drivers is that I run a MergedFB desktop at 2560x1024, and each screen is supposed to display it's own screensaver, but that's just speculation. Adam |