On Fri, Apr 19, 2002 at 01:26:40PM +0100, Major A wrote: > I'm using DRI on a G400 card with 16MB video RAM. When using graphics > extensively (FlightGear) in a high-resolution set-up (1600x1200, > 16bpp), the X server hangs after a few minutes of starting the > program. On 1280x1024, 16bpp, it can also hang, but it usually takes > hours before it does. The symptom is that the screen freezes, nothing > is updated (neither the GL window nor the xclock), only the pointer > works. It doesn't react to button presses, and the cursor doesn't > change as I move between windows, though. At this point, the fgfs > process vanishes, so there is nothing to kill apart from the X > server. I found that most of the time, it doesn't come back properly > after this hang, so I have to reboot the computer.
This sounds similar to a hand that I saw while testing the drmcommand branch. At that time the problem DID exist in both the branch and the trunk. I sent an e-mail to the list a few days ago explaining how to reproduce this problem with Quake 3. In that mail there were some instructions for enabling debug messages in the MGA driver. Could you please follow those steps (i.e., modify mgacontext.h and mga_xmesa.c), retry your FlightGear test and post your results? That way we can know if you're seeing the same issue that I saw. I suppose I should file a bug for this... -- Tell that to the Marines! _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
