From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by ug-out-1314.google.com with SMTP id s2so46666uge for ; Tue, 10 Apr 2007 23:17:04 -0700 (PDT) Message-ID: Date: Wed, 11 Apr 2007 14:17:04 +0800 From: "Zhao Forrest" Subject: Why kmem_cache_free occupy CPU for more than 10 seconds? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-linux-mm@kvack.org Return-Path: To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org List-ID: Hi, 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? Please let me know if you need any information. Thanks, Forrest -------------------------------------------------------------- BUG: soft lockup detected on CPU#1! Call Trace: [] softlockup_tick+0xdb/0xed [] update_process_times+0x42/0x68 [] smp_local_timer_interrupt+0x23/0x47 [] smp_apic_timer_interrupt+0x41/0x47 [] apic_timer_interrupt+0x66/0x6c [] kmem_cache_free+0x1c0/0x1cb [] free_buffer_head+0x2a/0x43 [] try_to_free_buffers+0x89/0x9d [] invalidate_mapping_pages+0x90/0x15f [] kill_bdev+0xe/0x21 [] __blkdev_put+0x4f/0x169 [] __fput+0xae/0x198 [] filp_close+0x5c/0x64 [] put_files_struct+0x6c/0xc3 [] do_exit+0x2d2/0x8b1 [] cpuset_exit+0x0/0x6c [] get_signal_to_deliver+0x427/0x456 [] do_notify_resume+0x9c/0x7a9 [] default_wake_function+0x0/0xe [] audit_syscall_exit+0x2cd/0x2ec [] int_signal+0x12/0x17 -------------------------------------------------------------- -- 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: email@kvack.org