public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: celeron2002@chile.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug in mm/slab.c
Date: Tue, 23 Nov 2004 18:02:08 -0500	[thread overview]
Message-ID: <1101250929.5207.1.camel@krustophenia.net> (raw)
In-Reply-To: <34591.200.113.104.46.1101247993.squirrel@mail.chile.com>

On Tue, 2004-11-23 at 19:13 -0300, celeron2002@chile.com wrote:
> Problem with chipset nforce in the boot
> Kernel 2.6.9-final in archlinux ( www.archlinux.org ) but compiled by myself.
> 
> nvidia: module license 'NVIDIA' taints kernel.
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module  1.0-6111  Tue Jul 27
> 07:55:38 PDT 2004
> kmem_cache_create: duplicate cache sgpool-8
> ------------[ cut here ]------------
> kernel BUG at mm/slab.c:1442!


Not only do you have the nvidia module loaded, but it looks like the
nvidia module caused your oops.

Did you see the line about 'module license NVIDIA taints kernel'?
Google for what this means and you will understand why this bug report
is offtopic.

Lee



  reply	other threads:[~2004-11-23 23:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 22:13 bug in mm/slab.c celeron2002
2004-11-23 23:02 ` Lee Revell [this message]
2004-11-24  0:02   ` Brent Casavant
2004-11-24  0:07     ` Lee Revell
2004-11-23 23:55 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2007-05-18  5:53 BUG " Jeff Garzik
2007-05-18  6:00 ` Satyam Sharma
2007-05-18  6:04 ` Andrew Morton
2004-11-23 22:12 bug " celeron

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=1101250929.5207.1.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=celeron2002@chile.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