From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with ESMTP id 2F2DC6B002D for ; Mon, 14 Nov 2011 14:54:17 -0500 (EST) Date: Mon, 14 Nov 2011 20:53:52 +0100 From: Jan Kara Subject: Re: [OOPS]: Kernel 3.1 (ext3?) Message-ID: <20111114195352.GB17328@quack.suse.cz> References: <20111110132929.GA11417@zeus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111110132929.GA11417@zeus> Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Watts Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org, Christoph Lameter , linux-mm@kvack.org Hi, On Thu 10-11-11 08:29:37, Andrew Watts wrote: > I had the following kernel panic today on 3.1 (machine was compiling code > unattended). It would appear to be a bug/regression introduced sometime > between 2.6.39.4 and 3.1. Hmm, the report is missing a line (top one) saying why the kernel actually crashed. Can you add that? Also it seems you are using SLUB allocator, right? This seems like a problem there so adding some CCs. Honza > ================ > > > EIP: 0060:[] EFLAGS: 00210082 CPU: 0 > EIP is at init_once+0x13/0x50 > EAX: f5406068 EBX: f5406000 ECX: c1962c63 EDX: c1781109 > ESI: f5406000 EDI: f5406000 EBP: f0d2dc6c ESP: f0d2dc68 > DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068 > Process ar (pid 17281, ti=f0d2c000 task=f3060c50 tast.ti=f0d2c000) > Stack: > f5c5aa00 f0d2dc7c c10d953b f5c5aa00 f6fa50c0 f0d2dca0 c10d97d6 00000000 > f5406000 f5406000 f5406000 00000000 00000000 f5c5aa00 f0d2dd34 c10dadf1 > f5803200 f1f5b2a0 f58b3030 f0d2dcd4 00000000 f0d2dccc 00000000 c114cd22 > Call Trace: > [] setup_object+0x4b/0x60 > [] new_slab+0x126/0x1d0 > [] T.1022+0x131/0x340 > [] ? ext3_alloc_inode+0x12/0x60 > [] ? ext3_getblk+0xd7/0x1d0 > [] ? wake_up_bit+0x57/0x60 > [] ? ext3_alloc_inode+0x12/0x60 > [] ? unlock_buffer+0x10/0x20 > [] kmem_cache_alloc+0x10a/0x120 > [] ? ext3_alloc_inode+0x12/0x60 > [] ? ext3_find_entry+0x3fe/0x5d0 > [] ext3_alloc_inode+0x12/0x60 > [] alloc_inode+0x1c/0x80 > [] new_inode_pseudo+0x8/0x30 > [] new_inode+0x12/0x40 > [] ext3_new_inode+0x4c/0x900 > [] ? journal_start+0x62/0xd0 > [] ? journal_start+0x90/0xd0 > [] ? ext3_journal_start_sb+0x29/0x50 > [] ext3_create+0x7c/0xe0 > [] vfs_create+0x93/0xb0 > [] do_last+0x38c/0x760 > [] path_openat+0x9a/0x340 > [] do_filp_open+0x30/0x80 > [] ? kmem_cache_alloc+0x95/0x120 > [] ? getname_flags+0x28/0x110 > [] ? alloc_fd+0x62/0xe0 > [] ? getname_flags+0xbb/0x110 > [] do_sys_open+0xed/0x1e0 > [] ? vfs_read+0xf5/0x160 > [] sys_open+0x29/0x40 > [] sysenter_do_call+0x12/0x22 > Code: 00 00 00 00 00 89 d0 5d c3 eb 0d 90 90 90 90 90 90 90 90 90 > 90 90 90 90 55 b9 63 2c 96 c1 89 e5 ba 09 11 78 c1 53 89 c3 8d 40 > 68 43 68 89 43 6c 8d 43 5c e8 cf 55 09 00 8d 43 7c b9 63 2c 96 > EIP: [] init_once+0x13/0x50 SS:ESP 0068:f0d2dc68 > CR2: 00000000f5406068 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Jan Kara SUSE Labs, CR -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org