From: rct@gherkin.frus.com (Bob_Tracy)
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at page_alloc.c:117!
Date: Wed, 7 Aug 2002 14:27:32 -0500 (CDT) [thread overview]
Message-ID: <m17cWSy-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <20020807143152.GA5991@louise.pinerecords.com> "from Tomas Szepe at Aug 7, 2002 04:31:52 pm"
Tomas Szepe wrote:
> > Please report this to Nvidia. The linux community does not support or
> > care about bugs reported on any boot when their binary only modules have
> > been loaded
>
> And in case you're wondering whether lkml people are being assholes about
> binary-only drivers and don't really want to help, note that this particular
> bug has been confirmed many times to indeed be caused by the Nvidia module.
Worse... When we outcast NVidia users trot over to the linux forum on
the NVidia website, the attitude of the fellow that responds to darned
near every posting might best be summarized as:
"The 2.5.X series is for kernel developers. If you fancy
yourself a kernel developer, you can fix the OS interface
routines yourself."
It's not clear from the limited amount of time I spend in that forum
whether that poster is an NVidia employee, but if so... FEH!!!
I supposed it *might* be possible that the source code NVidia *does*
provide can be patched to workaround the braindamage that lurks within
the binary-only module. Circumstantial evidence suggests the contrary,
or it would have already been done. Enough has changed within the
2.5.X memory management code that I'm reasonably certain the NVidia
driver problems will require modifications to code we *don't* have
source for.
Consider this an invitation for any NVidia employee "in the know" (who
also reads this list) to comment. Even a hearty "f*ck off" would beat
the world-class lettin' alone the linux community is currently getting.
Linux zealots who insist I should vote with my dollars are cordially
invited to suggest alternative video cards that (1) are fully
supported under Linux, and (2) perform as well as the NVidia cards do
(when the NVidia driver doesn't crash my system, that is). I have two
informal benchmarks I care about: the OpenGL "lament" screensaver, and
Unreal Tournament.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2002-08-07 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 13:09 PROBLEM: kernel BUG at page_alloc.c:117! Sergio Avila
2002-08-07 13:47 ` Adam Kropelin
2002-08-07 15:33 ` Alan Cox
2002-08-07 14:31 ` Tomas Szepe
2002-08-07 19:27 ` Bob_Tracy [this message]
2002-08-07 20:10 ` [OT] " J Sloan
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=m17cWSy-0005khC@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-kernel@vger.kernel.org \
/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