linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.68] Scalability issues
Date: Mon, 05 May 2003 10:05:00 -0400	[thread overview]
Message-ID: <3EB66F8C.8050402@nortelnetworks.com> (raw)
In-Reply-To: 20030505075118.GA352@codeblau.de

Felix von Leitner wrote:
> Thus spake David S. Miller (davem@redhat.com):

>>Either reproduce without the nvidia module loaded, or take
>>your report to nvidia.
>>
> 
> Thank you for this stunning display of unprofessionalism and zealotry.
> People like you keep free software alive.

He may not have put it as politely as you would like, but there really is no way 
to debug a problem in a kernel which has been tainted by binary-only drivers. 
That driver could have done literally anything to the kernel on loading.

Chris




-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  parent reply	other threads:[~2003-05-05 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 17:39 [2.5.68] Scalability issues Felix von Leitner
2003-05-04 18:16 ` Michael Buesch
2003-05-04 19:44 ` Felix von Leitner
2003-05-04 20:12   ` David S. Miller
2003-05-05  7:51     ` Felix von Leitner
2003-05-05  9:51       ` Carl-Daniel Hailfinger
2003-05-05 14:05       ` Chris Friesen [this message]
2003-05-06 18:44         ` Bill Davidsen
2003-05-06 20:36           ` Timothy Miller
2003-05-07  0:22           ` Carl-Daniel Hailfinger
2003-05-04 20:34   ` Tomas Szepe
2003-05-06 11:11 ` William Lee Irwin III
2003-05-06 11:46 ` William Lee Irwin III

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=3EB66F8C.8050402@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=felix-kernel@fefe.de \
    --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;
as well as URLs for NNTP newsgroup(s).