From: Christoph Lameter <clameter@sgi.com>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
Date: Mon, 21 May 2007 09:30:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705210917280.25871@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070520133505.46147.qmail@web52609.mail.re2.yahoo.com>
On Sun, 20 May 2007, Srihari Vijayaraghavan wrote:
> With no CONFIG_SLUB_DEBUG, things have slightly improved. No more panic. Good.
> Serial console is working. Good. But there is another problem:
Well this indicates that something destroys the sysfs pointer structure
that SLUB is using. Could you reenable CONFIG_SLUB_DEBUG and boot with the
option "slub_debug" on the kernel command line?
Also enable the list debug options in kernel hacking.
This should show up on the console since the failure is in slub_sysfs_init
which is long after the console has been enabled. I wonder why it did not
show so far?
> Freeing unused kernel memory: 308k freed
> BUG: spinlock bad magic on CPU#1, init/1
> lock: ffff81011ec0a100, .magic: ffff8101, .owner: <none>/-1, .owner_cpu: -1
>
> Call Trace:
> [<ffffffff802fc516>] _raw_spin_lock+0x22/0xf6
> [<ffffffff8026f684>] vma_adjust+0x219/0x454
> [<ffffffff8026f684>] vma_adjust+0x219/0x454
> [<ffffffff8026fe0d>] vma_merge+0x147/0x1f4
> [<ffffffff80270b55>] do_mmap_pgoff+0x414/0x7c7
> [<ffffffff8040aa34>] _spin_unlock_irq+0x24/0x27
> [<ffffffff8020f528>] sys_mmap+0xe5/0x110
> [<ffffffff80209dde>] system_call+0x7e/0x83
Hmmmm..... We have seen this before
http://marc.info/?l=linux-kernel&m=117891943401284&w=2
I suspect this is due to an interaction with other debug flags you have
set. What I see in your .config is
CONFIG_DEBUG_RT_MUTEXES=y
Try to switch this off if switching off the lockdep flags does not hel.
CONFIG_DEBUG_PI_LIST=y
Will go off with the above
# CONFIG_RT_MUTEX_TESTER is not set
Leave off
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
Try toggling if the disabling lockdep flags does not work.
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
I suspect the above are the main candidates for trouble. Could you
switch those off?
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
Debug kobject may be helpful.
CONFIG_DEBUG_BUGVERBOSE=y
next prev parent reply other threads:[~2007-05-21 16:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 13:35 Srihari Vijayaraghavan
2007-05-21 16:30 ` Christoph Lameter [this message]
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
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=Pine.LNX.4.64.0705210917280.25871@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.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 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®