From: Jens Axboe <axboe@suse.de>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: Andi Kleen <ak@suse.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219
Date: Tue, 10 May 2005 11:02:10 +0200 [thread overview]
Message-ID: <20050510090209.GJ21649@suse.de> (raw)
In-Reply-To: <1115713686.918.5.camel@localhost.localdomain>
On Tue, May 10 2005, Alexander Nyberg wrote:
> tis 2005-05-10 klockan 08:18 +0200 skrev Jens Axboe:
> > On Mon, May 09 2005, Andi Kleen wrote:
> > > On Mon, May 09, 2005 at 10:39:37PM +0200, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > I get this from 2.6.12-rc3-mm3 on a UP AMD64 box (Asus L5D), 100% of the time:
> > >
> > > Probably a generic bug. Block layer is passing some slab flag slab
> > > doesn't like.
> >
> > Some slab change, perhaps? There's nothing special about the init_bio()
> > slab call:
> >
> > bio_slab = kmem_cache_create("bio", sizeof(struct bio), 0,
> > SLAB_HWCACHE_ALIGN|SLAB_PANIC, NULL, NULL);
> >
> >
> > Hmm, this looks strange. That bug happens if:
> >
> > if ((!name) ||
> > in_interrupt() ||
> > (size < BYTES_PER_WORD) ||
> > (size > (1<<MAX_OBJ_ORDER)*PAGE_SIZE) ||
> > (dtor && !ctor)) {
> > printk(KERN_ERR "%s: Early error in slab %s\n",
> > __FUNCTION__, name);
> > BUG();
> > }
> >
> > It must be in_interrupt() triggering, perhaps something change in the
> > boot sequence?
> >
>
> The funny thing is that it seems to be the name being NULL, from the
> original post:
> kmem_cache_create: Early error in slab <NULL>
>
> When looking at the code I really can't see how that can be. Rafael,
> what setup is this compiled under?
Huh indeed, smells like bad code generation or hardware.
--
Jens Axboe
next prev parent reply other threads:[~2005-05-10 9:03 UTC|newest]
Thread overview: 16+ 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 [this message]
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 ` [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update] Rafael J. Wysocki
2005-05-10 18:22 ` 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
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 4:39 [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 li nux
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=20050510090209.GJ21649@suse.de \
--to=axboe@suse.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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