From: Lee Revell <rlrevell@joe-job.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Tim Fairchild <tim@bcs4me.com>,
Christoph Hellwig <hch@infradead.org>,
Sid Boyce <sboyce@blueyonder.co.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OT] NVIDIA Driver 1.0-6111 fix
Date: Sat, 04 Sep 2004 23:32:34 -0400 [thread overview]
Message-ID: <1094355154.6575.604.camel@krustophenia.net> (raw)
In-Reply-To: <200409050203.i8523X6W031952@localhost.localdomain>
On Sat, 2004-09-04 at 22:03, Horst von Brand wrote:
> > > I've never had an oops that was specifically caused by the nvidia
> > > module, tho I suppose it does happen.
>
> > And I have never seen one either.
>
> How do you know?
>
I don't know for sure. In the past week or two I saw two
OOPS-with-tainted-kernel posts, and in both cases the user was able to
reproduce the problem with an untainted kernel. But that was not my
point, I should have used a better example.
> > I am just using the OOPS'es as an
> > indication of how many Linux users use this driver.
>
> How do you know the OOPSes aren't caused (indirectly) by nVidia?
I don't, see above. But, this is offtopic.
> Sure, the
> incidence seems to have gone down, and perhaps lusers have learnt not to
> post OOPSes for tainted kernels...
>
Eh, I wouldn't call them lusers, posting an OOPS is complicated for a
non-geek, you can't expect everyone to get it 100% right the first time.
> > It's WAY more than
> > I expected.
>
> Now you confuse me... you see _many_ OOPSes with nVidia, but know for
> _sure_ nVidia has nothing to do with it?
I meant that the number of people using the nvidia driver was way more
than I would have thought. There are a *lot* of people gaming on Linux
these days, I had no idea. This is great.
Lee
next prev parent reply other threads:[~2004-09-05 3:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 0:17 NVIDIA Driver 1.0-6111 fix Sid Boyce
2004-09-04 6:28 ` Prakash K. Cheemplavam
2004-09-04 9:25 ` Dominik Karall
2004-09-04 9:32 ` Sid Boyce
2004-09-04 9:36 ` Christoph Hellwig
2004-09-04 9:54 ` Tim Fairchild
2004-09-04 9:58 ` Christoph Hellwig
2004-09-04 19:56 ` Lee Revell
2004-09-04 21:02 ` Tim Fairchild
2004-09-04 21:22 ` Lee Revell
2004-09-04 22:09 ` Tim Fairchild
2004-09-05 1:12 ` [OT] " Christian Kujau
2004-09-05 1:52 ` Lee Revell
2004-09-05 2:03 ` Horst von Brand
2004-09-05 3:32 ` Lee Revell [this message]
2004-09-05 5:29 ` [OT] " Tim Fairchild
2004-09-05 5:57 ` Lee Revell
2004-09-05 23:20 ` J.A. Magallon
2004-09-06 0:23 ` Lee Revell
2004-09-06 20:54 ` Alessandro Sappia
2004-09-05 12:03 ` Giuseppe Bilotta
2004-09-05 12:04 ` Alan Cox
2004-09-05 13:39 ` Grzegorz Kulewski
2004-09-05 14:37 ` Sid Boyce
2004-09-05 23:29 ` Chris Wedgwood
2004-09-04 21:22 ` Dominik Karall
2004-09-04 21:25 ` Lee Revell
2004-09-04 23:44 ` Paul Jakma
2004-09-05 6:27 ` Sid Boyce
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=1094355154.6575.604.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
--cc=tim@bcs4me.com \
--cc=vonbrand@inf.utfsm.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.