The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@suse.de>, Alexander Nyberg <alexn@dsv.su.se>,
	li nux <lnxluv@yahoo.com>
Subject: Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update]
Date: Tue, 10 May 2005 14:43:30 +0200	[thread overview]
Message-ID: <200505101443.31229.rjw@sisk.pl> (raw)
In-Reply-To: <20050509145424.6ffba49a.akpm@osdl.org>

Hi,

On Monday, 9 of May 2005 23:54, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > I get this from 2.6.12-rc3-mm3 on a UP AMD64 box (Asus L5D), 100% of the time:
> > 
> > ]--snip--[
> > ACPI: bus type pci registered
> > PCI: Using configuration type 1
> > mtrr: v2.0 (20020519)
> > kmem_cache_create: Early error in slab <NULL>
> > ----------- [cut here ] --------- [please bite here ] ---------
> > Kernel BUG at "mm/slab.c":1219
> > invalid operand: 0000 [1]
]--snip--[ 
> 
> Something kooky is happening.
> 
> Clearly init_bio() is not passing in a NULL `name' parameter.  Maybe the
> backtrace is screwed due to dopey gcc autoinlining and the bad caller is
> really biovec_init_slabs().  Try removing the
> __cacheline_aligned_mostly_readonly from the declaration of bvec_slabs[].

Heh, it boots without the __cacheline_aligned_mostly_readonly (ie the BUG is
only triggered if the __cacheline_aligned_mostly_readonly is present in the
declaration of bvec_slabs[]).  I've double-checked it.  Interesting ... ;-)

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  parent reply	other threads:[~2005-05-10 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 20:39 [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 Rafael J. Wysocki
2005-05-09 20:52 ` Andi Kleen
2005-05-10  6:18   ` Jens Axboe
2005-05-10  8:28     ` Alexander Nyberg
2005-05-10  9:02       ` Jens Axboe
2005-05-10 10:55     ` Andi Kleen
2005-05-09 21:54 ` Andrew Morton
2005-05-10 11:49   ` Rafael J. Wysocki
2005-05-10 12:43   ` Rafael J. Wysocki [this message]
2005-05-10 18:22     ` [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update] Andrew Morton
2005-05-10 21:11       ` Andi Kleen
2005-05-10 21:44         ` Christoph Lameter
2005-05-10 21:49           ` Andi Kleen
2005-05-10 22:01             ` Christoph Lameter
2005-05-10 22:15               ` Andi Kleen

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=200505101443.31229.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnxluv@yahoo.com \
    /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