From: "Zhao Forrest" <forrest.zhao@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Why kmem_cache_free occupy CPU for more than 10 seconds?
Date: Wed, 11 Apr 2007 17:14:46 +0800 [thread overview]
Message-ID: <ac8af0be0704110214qdca2ee9t3b44a17341e53730@mail.gmail.com> (raw)
In-Reply-To: <84144f020704102353r7dcc3538u2e34237d3496630e@mail.gmail.com>
I enable CONFIG_DEBUG_SLAB, but don't get any extra debug messages
related to slab.
Is there other switch that I need to turn on?
Thanks,
Forrest
BUG: soft lockup detected on CPU#6!
Call Trace:
<IRQ> [<ffffffff800b3834>] softlockup_tick+0xdb/0xed
[<ffffffff80093edf>] update_process_times+0x42/0x68
[<ffffffff80074897>] smp_local_timer_interrupt+0x23/0x47
[<ffffffff80074f59>] smp_apic_timer_interrupt+0x41/0x47
[<ffffffff8005c7c2>] apic_timer_interrupt+0x66/0x6c
<EOI> [<ffffffff80043b09>] invalidate_mapping_pages+0xe1/0x15f
[<ffffffff80043afa>] invalidate_mapping_pages+0xd2/0x15f
[<ffffffff800d5bea>] kill_bdev+0xe/0x21
[<ffffffff800d6110>] __blkdev_put+0x4f/0x169
[<ffffffff80012785>] __fput+0xae/0x198
[<ffffffff80023ca6>] filp_close+0x5c/0x64
[<ffffffff80038e33>] put_files_struct+0x6c/0xc3
[<ffffffff8001543d>] do_exit+0x2d2/0x8b1
[<ffffffff80047932>] cpuset_exit+0x0/0x6c
[<ffffffff8002b30f>] get_signal_to_deliver+0x427/0x456
[<ffffffff80059b9e>] do_notify_resume+0x9c/0x7a9
[<ffffffff8008776d>] default_wake_function+0x0/0xe
[<ffffffff800b2b79>] audit_syscall_exit+0x2cd/0x2ec
[<ffffffff8005be62>] int_signal+0x12/0x17
On 4/11/07, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On 4/11/07, Zhao Forrest <forrest.zhao@gmail.com> wrote:
> > We're using RHEL5 with kernel version 2.6.18-8.el5.
> > When doing a stress test on raw device for about 3-4 hours, we found
> > the soft lockup message in dmesg.
> > I know we're not reporting the bug on the latest kernel, but does any
> > expert know if this is the known issue in old kernel? Or why
> > kmem_cache_free occupy CPU for more than 10 seconds?
>
> Sounds like slab corruption. CONFIG_DEBUG_SLAB should tell you more.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-11 9:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 6:17 Zhao Forrest
2007-04-11 6:53 ` Pekka Enberg
2007-04-11 9:14 ` Zhao Forrest [this message]
2007-04-11 9:53 ` Paul Jackson
2007-04-11 10:06 ` Peter Zijlstra
2007-04-11 10:10 ` Zhao Forrest
2007-04-11 10:16 ` Peter Zijlstra
2007-04-11 16:23 ` Chuck Ebbert
2007-04-11 16:44 ` Badari Pulavarty
2007-04-11 9:53 ` Zhao Forrest
2007-04-11 10:38 ` Peter Zijlstra
2007-04-11 16:35 ` Ken Chen
2007-04-12 6:17 ` Zhao Forrest
2007-04-11 22:30 ` Andrew Morton
2007-04-12 7:39 ` Peter Zijlstra
2007-04-12 7:55 ` Andrew Morton
2007-04-12 9:19 ` Peter Zijlstra
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=ac8af0be0704110214qdca2ee9t3b44a17341e53730@mail.gmail.com \
--to=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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