The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Jens Axboe <axboe@suse.de>
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 12:55:06 +0200	[thread overview]
Message-ID: <20050510105506.GF25612@wotan.suse.de> (raw)
In-Reply-To: <20050510061858.GB21649@suse.de>

> 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?

I would add a printk for all arguments on top of kmem_cache_create
and decompose the big if () into smaller if (...) BUG() so that you
can see which condition triggers exactly.

Then if you suspect compiler issues you can edit the Makefile and
recompile the kernel with -O1

Rafael, can you try that perhaps?

-Andi

  parent reply	other threads:[~2005-05-10 10:55 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
2005-05-10 10:55     ` Andi Kleen [this message]
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=20050510105506.GF25612@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --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