From: Nick Piggin <nickpiggin@yahoo.com.au>
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
Date: Sun, 18 Apr 2004 15:12:36 +1000 [thread overview]
Message-ID: <40820E44.7010208@yahoo.com.au> (raw)
In-Reply-To: <E1BF0rr-0007TG-Rh@server.cyberhostplus.biz>
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
next prev parent reply other threads:[~2004-04-18 5:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 16:14 2.6.6-rc1 caused dedicated Quake 3 server to core dump Stephen Lee
2004-04-17 17:59 ` Francois Romieu
2004-04-18 1:13 ` Steve Lee
2004-04-18 5:12 ` Nick Piggin [this message]
2004-04-17 18:17 ` Christophe Saout
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40820E44.7010208@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=steve@tuxsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox