From: "Håvard Skinnemoen" <hskinnemoen@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Haavard Skinnemoen" <hskinnemoen@atmel.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at mm/slub.c:3689!
Date: Mon, 11 Jun 2007 19:11:16 +0200 [thread overview]
Message-ID: <1defaf580706111011w641b26fbu68d6d34028f6e953@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706110946430.15910@schroedinger.engr.sgi.com>
On 6/11/07, Christoph Lameter <clameter@sgi.com> wrote:
> Ahhh... I see its the same phenomenon as before but triggered by
> a different cause.
>
> If you set the align to 32 then the first kmalloc slabs of size
>
> 8
> 16
> 32
>
> are all of the same size which leads to duplicate files in sysfs.
Yes, that seems to be the problem.
> Does this patch fix it?
Unfortunately, no. But I get a different error message; see below...
Also unfortunately, I won't be able to do any more testing until I get
back to work tomorrow -- I'm currently at home and I can't reset my
board remotely (Doh! Why didn't I set panic_timeout...)
Haavard
kobject_add failed for :0000016 with -EEXIST, don't try to register
things with the same name in the same directory.
Call trace:
[<9000f14e>] dump_stack+0x1a/0x24
[<90093128>] kobject_shadow_add+0xc4/0xe8
[<90093154>] kobject_add+0x8/0xc
[<9003dec4>] sysfs_slab_add+0xb0/0xf0
[<900046c6>] slab_sysfs_init+0x26/0x78
[<900003f0>] kernel_init+0x74/0x1c0
[<90015cd4>] do_exit+0x0/0x52c
------------[ cut here ]------------
kernel BUG at /home/hskinnemoen/git/linux/mm/slub.c:3686!
Oops: Kernel BUG, sig: 9 [#1]
FRAME_POINTER chip: 0x01f:0x1e82 rev 0
Modules linked in:
PC is at slab_sysfs_init+0x28/0x78
LR is at 0x9014e654
pc : [<900046c8>] lr : [<9014e654>] Not tainted
sp : 901cbf98 r12: ffffffef r11: 00000001
r10: 00000001 r9 : 00000000 r8 : 9014e654
r7 : 901cbf98 r6 : 9014a2b4 r5 : 00000000 r4 : 00000000
r3 : 00000000 r2 : 90015cd4 r1 : 9000b4d0 r0 : 00000000
Flags: qvNzc
Mode bits: hrje....g
CPU Mode: Supervisor
Process: swapper [1] (task: 901c9000 thread: 901ca000)
Stack: (0x901cbf98 to 0x901cc000)
bf80: 900003f0 901cbfdc
bfa0: 90009b20 00000000 00000000 00000000 00000000 00000000 00400000 9000ebd0
bfc0: 9000ebd0 901cc000 00000000 00000000 00000000 00000000 00000000 90015cd4
bfe0: 00000000 00000000 00000000 00000000 00000000 90015cd4 9000037c 00000000
Call trace:
[<900003f0>] kernel_init+0x74/0x1c0
[<90015cd4>] do_exit+0x0/0x52c
Kernel panic - not syncing: Attempted to kill init!
next prev parent reply other threads:[~2007-06-11 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 14:19 Haavard Skinnemoen
2007-06-11 15:38 ` Paul Mundt
2007-06-11 15:58 ` Håvard Skinnemoen
2007-06-11 16:19 ` Christoph Lameter
2007-06-11 16:43 ` Håvard Skinnemoen
2007-06-11 16:49 ` Christoph Lameter
2007-06-11 17:11 ` Håvard Skinnemoen [this message]
2007-06-11 17:52 ` Christoph Lameter
2007-06-11 18:22 ` Håvard Skinnemoen
2007-06-11 18:32 ` Christoph Lameter
2007-06-11 19:04 ` Håvard Skinnemoen
2007-06-11 19:11 ` Christoph Lameter
2007-06-11 19:35 ` Håvard Skinnemoen
2007-06-11 19:40 ` Christoph Lameter
2007-06-11 19:53 ` Håvard Skinnemoen
2007-06-12 3:16 ` Christoph Lameter
2007-06-12 8:55 ` Haavard Skinnemoen
2007-06-12 10:16 ` Haavard Skinnemoen
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=1defaf580706111011w641b26fbu68d6d34028f6e953@mail.gmail.com \
--to=hskinnemoen@gmail.com \
--cc=clameter@sgi.com \
--cc=hskinnemoen@atmel.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
all inboxes | Powered by JetHome®