Message-ID: <40820E44.7010208@yahoo.com.au>
Date: Sun, 18 Apr 2004 15:12:36 +1000
From: Nick Piggin <nickpiggin@yahoo.com.au>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040401 Debian/1.6-4
MIME-Version: 1.0
To: Steve Lee <steve@tuxsoft.com>
CC: "'Francois Romieu'" <romieu@fr.zoreil.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6-rc1 caused dedicated Quake 3 server to core dump
References: <E1BF0rr-0007TG-Rh@server.cyberhostplus.biz>
In-Reply-To: <E1BF0rr-0007TG-Rh@server.cyberhostplus.biz>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1278
Lines: 28

Steve Lee wrote:
> Ah, I meant to include that in my first email.  It's the latest NVidia
> driver 1.0-5336.  I know, I know, but it's worked fine with 2.6.5 and all
> previous.  Also, just the dedicated quake 3 server core dumped, the quake 3
> client running on the same machine did not crash.  At the time of the crash,
> there were four clients connected to the quake 3 server.  I realize the
> NVidia driver could have corrupted some memory some where else, but if
> that's the case, I would have thought it would have shown this behavior
> previous, and not just with 2.6.6-rc1.  Unless of course, something in
> 2.6.6-rc1 specifically altered something the NVidia driver makes use of.  I
> guess.  :-) 
> 

Hi Steve,
Unfortuately the nvidia driver means nobody is likely to look
into your problem - it is just not a good use of their time.
It would be very helpful if you could try to reproduce the oops
without the nvidia driver loaded though.

It should be possible if the nvidia driver isn't the cause of
the problem.

Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/