From: Jens Osterkamp <Jens.Osterkamp@gmx.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [BUG] in 2.6.25-rc3 with 64k page size and SLUB_DEBUG_ON
Date: Thu, 6 Mar 2008 23:21:55 +0100 [thread overview]
Message-ID: <200803062321.55581.Jens.Osterkamp@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803061354210.15083@schroedinger.engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 2336 bytes --]
> Then check 2.6.22 and specify the boot parameter "slub_debug". Make sure
> to compile the kernel with slub support. Is there any way you could get
With 2.6.22, slub on and slub_debug on the command line I get
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes0005416c/2
Call Trace:
[c00000000ff87ce8] [c00000000000f2cc] .show_stack+0x68/0x1b0 (unreliable)
[c00000000ff87d88] [c000000000347d3c] .schedule+0xa4/0x8f0
[c00000000ff87e88] [c0000000003486f4] .wait_for_completion+0xd8/0x174
[c00000000ff87f48] [c000000000071770] .kthreadd+0x124/0x1b8
[c00000000ff87fd8] [c0000000000256f8] .kernel_thread+0x4c/0x68
BUG: scheduling while atomic: kthreadd/0x0005416c/2
Call Trace:
[c00000000ff87da8] [c00000000000f2cc] .show_stack+0x68/0x1b0 (unreliable)
[c00000000ff87e48] [c000000000347d3c] .schedule+0xa4/0x8f0
[c00000000ff87f48] [c0000000000716e0] .kthreadd+0x94/0x1b8
[c00000000ff87fd8] [c0000000000256f8] .kernel_thread+0x4c/0x68
BUG: scheduling while atomic: kthreadd/0x0005416c/2
Call Trace:
[c00000000ff87ce8] [c00000000000f2cc] .show_stack+0x68/0x1b0 (unreliable)
[c00000000ff87d88] [c000000000347d3c] .schedule+0xa4/0x8f0
[c00000000ff87e88] [c0000000003486f4] .wait_for_completion+0xd8/0x174
[c00000000ff87f48] [c000000000071770] .kthreadd+0x124/0x1b8
[c00000000ff87fd8] [c0000000000256f8] .kernel_thread+0x4c/0x68
BUG: scheduling while atomic: kthreadd/0x0183eeb8/4
Call Trace:
[c00000000ff9bf10] [c00000000000f2cc] .show_stack+0x68/0x1b0 (unreliable)
[c00000000ff9bfb0] [c000000000347d3c] .schedule+0xa4/0x8f0
[c00000000ff9c0b0] [c000000000071960] .kthread+0x40/0xc4
[c00000000ff9c140] [c0000000000256f8] .kernel_thread+0x4c/0x68
BUG: scheduling while atomic: kthreadd/0x0005416c/2
Call Trace:
[c00000000ff87da8] [c00000000000f2cc] .show_stack+0x68/0x1b0 (unreliable)
[c00000000ff87e48] [c000000000347d3c] .schedule+0xa4/0x8f0
[c00000000ff87f48] [c0000000000716e0] .kthreadd+0x94/0x1b8
[c00000000ff87fd8] [c0000000000256f8] .kernel_thread+0x4c/0x68
> us further information about the problem?
Sure, what do you need ?
The system is a Cell Blade with 2G memory, hence numa support enabled.
I built the 2.6.22 with cell_defconfig and manually selected SLUB.
Gruß,
Jens
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-06 22:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 13:47 Jens Osterkamp
2008-03-06 19:55 ` Christoph Lameter
2008-03-06 21:07 ` Jens Osterkamp
2008-03-06 21:50 ` Christoph Lameter
2008-03-06 21:52 ` Jens Osterkamp
2008-03-06 21:56 ` Christoph Lameter
2008-03-06 22:00 ` Pekka Enberg
2008-03-06 22:04 ` Pekka Enberg
2008-03-06 22:07 ` Jens Osterkamp
2008-03-06 22:20 ` Christoph Lameter
2008-03-06 22:24 ` Pekka Enberg
2008-03-07 12:20 ` Jens Osterkamp
2008-03-07 12:40 ` Pekka J Enberg
2008-03-07 12:44 ` Pekka J Enberg
2008-03-07 22:18 ` Jens Osterkamp
2008-03-07 22:30 ` Jens Osterkamp
2008-03-07 22:59 ` Christoph Lameter
2008-03-12 15:19 ` Jens Osterkamp
2008-03-12 23:34 ` Christoph Lameter
2008-03-18 16:44 ` Jens Osterkamp
2008-03-18 17:45 ` Christoph Lameter
2008-03-18 17:51 ` Pekka Enberg
2008-03-06 22:25 ` Jens Osterkamp
2008-03-07 22:09 ` Jens Osterkamp
2008-03-06 22:21 ` Jens Osterkamp [this message]
2008-03-06 21:27 ` Pekka Enberg
2008-03-06 21:45 ` Ingo Molnar
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=200803062321.55581.Jens.Osterkamp@gmx.de \
--to=jens.osterkamp@gmx.de \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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