public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Anthony Russo., a.k.a. Stupendous Man" <anthony.russo@verizon.net>
To: Willy Tarreau <willy@w.ods.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 BUG in page_alloc.c:91
Date: Thu, 08 Aug 2002 12:15:35 -0400	[thread overview]
Message-ID: <3D529927.2040609@verizon.net> (raw)
In-Reply-To: 20020808160712.GA18664@alpha.home.local

Thank you very much. As I suspected, the tainted driver is
the one I use for my NetGear ethernet card (not nvidia :)
I have switched to using the standard netgear driver that
comes with linux and won't taint the kernel. I am now
rebooting and if the problem reoccurs I will follow up
with an email.

Thank you all for the support.

-- tony

Willy Tarreau wrote:

>On Thu, Aug 08, 2002 at 11:45:15AM -0400, Anthony Russo., a.k.a. Stupendous Man wrote:
> 
>  
>
>>Is there a way to tell which module it is that is setting the taint flag?
>>I can load each module one by one and check after each if the taint flag
>>is set, but I just need to know how to tell it is set.
>>    
>>
>
>Modinfo could help you by telling you the licence for each module.
>In the worst case, manually unload them all, and reload them one at a time.
>Modprobe will issue a warning when loading such a module.
>
>BTW, my apologies for doubting about a removed nvidia driver ;-)
>
>Regards,
>Willy
>
>
>  
>

-- 
"Surrender to the Void."
<http://162.83.145.190:8080/%7Eapr/surrenderToTheVoid.mp3> -- John Lennon



  reply	other threads:[~2002-08-08 16:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  2:45 2.4.19 BUG in page_alloc.c:91 Anthony Russo., a.k.a. Stupendous Man
2002-08-08  2:50 ` Rik van Riel
2002-08-08  2:54   ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08  7:55     ` Willy Tarreau
2002-08-08 15:42       ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 19:43         ` Alan Cox
2002-08-08 18:26           ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 20:04             ` Alan Cox
2002-08-08 12:38 ` Alan Cox
2002-08-08 12:19   ` [OT] " Andreas Steinmetz
2002-08-08 13:41     ` Alan Cox
2002-08-09  9:14     ` Keith Owens
2002-08-08 15:45   ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 16:07     ` Willy Tarreau
2002-08-08 16:15       ` Anthony Russo., a.k.a. Stupendous Man [this message]
2002-08-08 15:56   ` 2.4.19 BUG in page_alloc.c:91 -- NOT NVidia driver! Anthony Russo., a.k.a. Stupendous Man
2002-08-14 15:19 ` 2.4.19 BUG in page_alloc.c:91 Ingo Saitz
  -- strict thread matches above, loose matches on Subject: below --
2002-08-27 12:47 Salvador Eduardo Tropea

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=3D529927.2040609@verizon.net \
    --to=anthony.russo@verizon.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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