From: Andi Kleen <ak@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
axboe@suse.de
Subject: Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219
Date: Mon, 9 May 2005 22:52:52 +0200 [thread overview]
Message-ID: <20050509205251.GK25167@wotan.suse.de> (raw)
In-Reply-To: <200505092239.37834.rjw@sisk.pl>
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.
-Andi
>
> ]--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]
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.12-rc3-mm3
> RIP: 0010:[<ffffffff80179eeb>] <ffffffff80179eeb>{kmem_cache_create+139}
> RSP: 0000:ffff810001ca1eb8 EFLAGS: 00010292
> RAX: 0000000000000034 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000dd3 RDI: ffffffff804167e0
> RBP: 0000000000000005 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000010 R11: 0000000000000008 R12: 0000000000042000
> R13: 0000000000000000 R14: 0000ffffffff8010 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffffffff8055a840(0000) knlGS:0000000000000000
> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000004000 CR3: 0000000000101000 CR4: 00000000000006e0
> Process swapper (pid: 1, threadinfo ffff810001ca0000, task ffff810001c5a7a0)
> Stack: fffffffffffffff8 0000000000000000 0000000000000000 0000000000000000
> 0000000000000010 0000000000000000 0000000000000005 0000000000000006
> 00000000ffffffff 0000ffffffff8010
> Call Trace:<ffffffff8057a11d>{init_bio+93} <ffffffff8010c0f2>{init+178}
> <ffffffff8010fc37>{child_rip+8} <ffffffff8010c040>{init+0}
> <ffffffff8010fc2f>{child_rip+0}
>
>
> 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"
next prev parent reply other threads:[~2005-05-09 20:52 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 [this message]
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 ` [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=20050509205251.GK25167@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