From: Tim 'Tool-M. T. <ti...@to...> - 2001-01-13 06:49:36
|
100% reproducable by hitting Ctrl-Alt-Bkspc for me. 2.4.0 w CVS from 1/8/2001 Andrew McCall wrote: > I seem to be able to replicate the console corruption > bug I put on the bug tracker: > > http://sourceforge.net/bugs/?func=detailbug&bug_id=127622&group_id=387 > > Put simply, if I run a DRI enabled X server with the > Radeon driver, and then kill the X server from the > console(or it dies on its own), the console becomes > corrupted. > > Has anyone else experienced this behavoir? I attempted > a clean DRI install, and experienced the same results. > My sys config is the exact same, only now I'm running > 2.4-release, w/ CVS from 1/12/2001. The console > corruption bug I'm describing has been around since > the original Radeon driver release, but it duplicates > reliably under these conditions, for me at least. I'll > look into it some more to make sure I'm not doing > anything stupid, but for as far as I can tell, this is > it. I find that I get the following error quite a bit > also: > > [drm:radeon_freelist_get] *ERROR* returning NULL! > > And the following when the console dies: > > [drm:drm_release] *ERROR* Process 279 dead, freeing > lock for context 1 > > This is the only problem I'm having with the driver. > quake3 runs nice(actually faster than in windows under > specific conditions, believe it or not), gears works, > general success! > > ===== > ---- > This sentence contains exactly threee erors. > > Andrew McCall - amc...@ya... > > __________________________________________________ > Do You Yahoo!? > Get email at your own domain with Yahoo! Mail. > http://personal.mail.yahoo.com/ > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/lists/listinfo/dri-devel -- Tim Taylor ti...@to... |