From: "Steve Lee" <steve@tuxsoft.com>
To: "'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: Sat, 17 Apr 2004 20:13:05 -0500 [thread overview]
Message-ID: <E1BF0rr-0007TG-Rh@server.cyberhostplus.biz> (raw)
In-Reply-To: <20040417195930.A16784@electric-eye.fr.zoreil.com>
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. :-)
Steve
-----Original Message-----
From: Francois Romieu [mailto:romieu@fr.zoreil.com]
Sent: Saturday, April 17, 2004 1:00 PM
To: Stephen Lee
Cc: linux-kernel@vger.kernel.org; steve@tuxsoft.com
Subject: Re: 2.6.6-rc1 caused dedicated Quake 3 server to core dump
Stephen Lee <slee@tuxsoft.com> :
> For years now, I've been running a dedicated Quake 3 server on my linux
> box. Last night, was the first time I've ever seen a core dump with
> Quake. 2.6.5 was and is now running fine, but under 2.6.6-rc1 it core
> dumped within about 30 minutes with the attached dmesg output. I am
Which binary module are you using ?
--
Ueimor
next prev parent reply other threads:[~2004-04-18 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 16:14 Stephen Lee
2004-04-17 17:59 ` Francois Romieu
2004-04-18 1:13 ` Steve Lee [this message]
2004-04-18 5:12 ` Nick Piggin
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=E1BF0rr-0007TG-Rh@server.cyberhostplus.biz \
--to=steve@tuxsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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
all inboxes | Powered by JetHome®