From: David Miller <davem@davemloft.net>
To: mroos@linux.ee
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
clameter@sgi.com
Subject: Re: slab hang on boot
Date: Mon, 14 May 2007 15:11:48 -0700 (PDT) [thread overview]
Message-ID: <20070514.151148.45744375.davem@davemloft.net> (raw)
In-Reply-To: <Pine.SOC.4.64.0705142133190.17204@math>
From: Meelis Roos <mroos@linux.ee>
Date: Mon, 14 May 2007 21:36:42 +0300 (EEST)
> Sorry, I could not test the parport patch yet - I did git upgrade as of
> yesterday and the kernel hangs on boot. boot -p reveals the following
> slab panic:
Please enable SLUB to work around this for now, SLAB wants
LARGE_ALLOCS enabled when it really shouldn't require that
for a 512K or 1MB SLAB when PAGE_SIZE==8192 :-(
> kmem_cache_create: Early error in slab tsb_512KB
> kernel BUG at mm/slab.c:2165!
Christoph, this is why I had to have LARGE_ALLOCS enabled on sparc64
all this time, for that MAX_OBJ_ORDER logic in mm/slab.c in order
to get 512K and 1MB slab caches usable.
This inconsistency is painful for platforms. If I enable LARGE_ALLOCS
on sparc64 then SLAB works but it's a total waste for SLUB.
Right now if I enable LARGE_ALLOCS, SLUB will break again due to
that KMALLOC_SHIFT_HIGH bug we fixed the other week, Christophe
can you at least push that fix to Linus if you haven't already?
Thanks.
next parent reply other threads:[~2007-05-14 22:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOC.4.64.0705142133190.17204@math>
2007-05-14 22:11 ` David Miller [this message]
2007-05-14 23:46 ` slab hang on boot Christoph Lameter
2007-05-15 0:15 ` Andrew Morton
2007-05-15 23:33 ` Andrew Morton
2007-05-15 23:45 ` Christoph Lameter
2007-05-15 23:56 ` Andrew Morton
2007-05-16 0:14 ` David Miller
2007-05-16 0:29 ` Andrew Morton
2007-05-16 0:38 ` David Miller
2007-05-16 1:00 ` Christoph Lameter
2007-05-16 1:03 ` David Miller
2007-05-16 6:43 ` David Miller
2007-05-16 0:51 ` Christoph Lameter
2007-05-16 0:50 ` Christoph Lameter
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=20070514.151148.45744375.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=sparclinux@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