From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, Hugh Dickins <hugh@veritas.com>,
Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>,
Oliver Xymoron <oxymoron@waste.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
Date: Tue, 22 May 2007 09:07:39 +0200 [thread overview]
Message-ID: <20070522070738.GI4705@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0705211524060.29480@schroedinger.engr.sgi.com>
On Mon, May 21 2007, Christoph Lameter wrote:
> Ok booting SLUB without "slub_debug" and having
>
> CONFIG_DEBUG_LOCK_ALLOC
> CONFIG_LOCKDEP
>
> will trigger the problem.
>
> So I guess the issue is that lockdep does a slab alloc while we get the
> slab lock during slab alloc?
If I have CONFIG_SLUB_DEBUG set, then box boots fine. If I don't have it
set, then it hard hangs sometime after boot:
[...]
ReiserFS: sda2: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 180k freed
which is usually followed by messages bringing up the network link, etc.
Let me know which tests you want run, or which patches to try.
--
Jens Axboe
next prev parent reply other threads:[~2007-05-22 7:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 13:35 [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub Srihari Vijayaraghavan
2007-05-21 16:30 ` Christoph Lameter
2007-05-21 17:41 ` Hugh Dickins
2007-05-21 18:25 ` Christoph Lameter
2007-05-21 18:44 ` Hugh Dickins
2007-05-21 18:48 ` Christoph Lameter
2007-05-21 19:00 ` Jens Axboe
2007-05-21 19:06 ` Hugh Dickins
2007-05-21 19:09 ` Jens Axboe
2007-05-21 19:13 ` Christoph Lameter
2007-05-21 19:26 ` Jens Axboe
2007-05-21 19:29 ` Hugh Dickins
2007-05-21 19:34 ` Christoph Lameter
2007-05-21 22:27 ` Christoph Lameter
2007-05-21 23:46 ` Christoph Lameter
2007-05-22 7:07 ` Jens Axboe [this message]
2007-05-22 8:26 ` Srihari Vijayaraghavan
2007-05-22 9:24 ` Ingo Molnar
2007-05-22 11:01 ` Srihari Vijayaraghavan
2007-05-22 11:20 ` Ingo Molnar
2007-05-22 11:26 ` Srihari Vijayaraghavan
2007-05-22 13:01 ` Hugh Dickins
2007-05-22 15:36 ` Jens Axboe
2007-05-22 18:30 ` Christoph Lameter
2007-05-22 20:10 ` Jens Axboe
2007-05-22 22:15 ` Srihari Vijayaraghavan
2007-05-22 22:25 ` Christoph Lameter
2007-05-23 7:11 ` Jens Axboe
2007-05-23 17:04 ` Christoph Lameter
2007-05-24 7:25 ` Jens Axboe
2007-05-24 16:55 ` Christoph Lameter
2007-05-25 6:12 ` Jens Axboe
2007-05-25 13:40 ` Christoph Lameter
2007-05-25 14:00 ` Jens Axboe
2007-05-26 1:52 ` Christoph Lameter
2007-05-26 2:49 ` Srihari Vijayaraghavan
2007-05-23 10:18 ` Srihari Vijayaraghavan
2007-05-23 17:10 ` Christoph Lameter
2007-05-23 17:19 ` Christoph Lameter
2007-05-23 22:23 ` Srihari Vijayaraghavan
2007-05-23 22:32 ` Christoph Lameter
2007-05-24 13:12 ` Srihari Vijayaraghavan
2007-05-24 16:58 ` Christoph Lameter
2007-05-24 21:30 ` Srihari Vijayaraghavan
2007-05-24 22:19 ` Christoph Lameter
2007-05-24 22:39 ` Srihari Vijayaraghavan
2007-05-21 19:04 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2007-05-20 3:09 Srihari Vijayaraghavan
2007-05-20 7:12 ` Christoph Lameter
2007-05-20 7:40 ` Srihari Vijayaraghavan
2007-05-20 13:24 ` Satyam Sharma
2007-05-20 13:37 ` Srihari Vijayaraghavan
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=20070522070738.GI4705@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oxymoron@waste.org \
--cc=sriharivijayaraghavan@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.