From: Steven Walter <srwalter@ya...> - 2001-08-04 16:12:11
On Sat, Aug 04, 2001 at 01:01:24AM -0600, Bill Currie wrote:
> I get similar lockups using quakeforge on my G200, however I can /always/ ssh
> in and just kill the program (nq-glx or qw-client-glx). Here is a what I got
> from a recent lockup:
> Failed to upload texture, sz 174592
> Memory heap (nil):
> heap == 0
> End of memory blocks
> Received signal 11, exiting...
> Received signal 15, exiting...
> recursive shutdown
> NOTE: I /believe/ (no idea, qf is usually running full-screen at the time) that
> the signal 11 is printed /after/ I run "killall qw-client-glx". Also note that
> I don't always get the upload errors when I get a lockup. This time, I got 8
> of those messages. Oh, I should point out that I am using the MGA apg
> texturing patches on cvs trunk (a week or two old).
> My belief is that libGL is getting a seg fault while it is holding a lock, qf
> catches the signal and tries to shut down. This involves trying to cleanly
> shut down the glx interface which (if I'm correct about the lock) is causing X
> to wedge.
I get very similar lockups to this with quake3 arena and a Voodoo3 3000.
Quake3 locks up, either on exiting the game or changing graphics
settings, which hangs X. I have to log in over a serial console, and
"killall -9 q3demo.x86". After I do that, X comes back to life, and
quake3 reports a "DOUBLE SIGNAL FAULT". I don't have the exact output,
but I could surely come across it.
This lock up is one of the most irritating things I come across in DRI.
I've reported it several times before, but no one has expressed an
interest in fixing it.
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell