From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx168.postini.com [74.125.245.168]) by kanga.kvack.org (Postfix) with SMTP id 426306B0034 for ; Wed, 21 Aug 2013 00:46:29 -0400 (EDT) Message-ID: <5214461D.9000009@intel.com> Date: Tue, 20 Aug 2013 21:46:21 -0700 From: Dave Hansen MIME-Version: 1.0 Subject: Re: [BUG REPORT]kernel panic with kmemcheck config References: <5212D7F2.3020308@huawei.com> <521381A9.4020501@intel.com> <521429D5.8070003@huawei.com> In-Reply-To: <521429D5.8070003@huawei.com> Content-Type: text/plain; charset=gb18030 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Libin Cc: Vegard Nossum , Pekka Enberg , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Li Zefan , guohanjun@huawei.com, zhangdianfang@huawei.com On 08/20/2013 07:45 PM, Libin wrote: > [ 3.158023] ------------[ cut here ]------------ > [ 3.162626] WARNING: CPU: 0 PID: 1 at arch/x86/mm/kmemcheck/kmemcheck.c:634 kmemcheck_fault+0xb1/0xc0() ... > [ 3.314877] [] ? kmemcheck_trap+0x17/0x30 > [ 3.320507] <> <#DB> [] do_debug+0x16a/0x1c0 > [ 3.327029] [] debug+0x25/0x40 > [ 3.331714] [] ? rb_insert_color+0xcc/0x150 > [ 3.337518] <> [] sysfs_link_sibling+0xa8/0xf0 > [ 3.344124] [] ? __sysfs_add_one+0x6a/0x120 > [ 3.349931] [] __sysfs_add_one+0x77/0x120 > [ 3.355563] [] sysfs_add_one+0x26/0xe0 > [ 3.360937] [] create_dir+0x7c/0xd0 > [ 3.366050] [] sysfs_create_dir+0x93/0xd0 > [ 3.371684] [] kobject_add_internal+0xe9/0x270 > [ 3.377748] [] kobject_add_varg+0x38/0x60 > [ 3.383380] [] ? kobject_add+0x1e/0x70 > [ 3.388751] [] kobject_add+0x44/0x70 > [ 3.393954] [] ? device_add+0xc2/0x580 > [ 3.399328] [] device_add+0xd3/0x580 > [ 3.404529] [] ? device_initialize+0xab/0xc0 > [ 3.410422] [] device_register+0x19/0x20 > [ 3.415971] [] init_memory_block+0xfb/0x120 > [ 3.421776] [] add_memory_section+0xdc/0x140 > [ 3.427672] [] memory_dev_init+0xa3/0xc1 > [ 3.433264] [] driver_init+0x2f/0x31 > [ 3.438466] [] do_basic_setup+0x29/0xce > [ 3.443929] [] ? sched_init_smp+0x14f/0x156 > [ 3.449735] [] kernel_init_freeable+0x20d/0x291 > [ 3.455886] [] ? rest_init+0x80/0x80 > [ 3.461084] [] kernel_init+0x9/0x180 > [ 3.466285] [] ret_from_fork+0x7c/0xb0 > [ 3.471659] [] ? rest_init+0x80/0x80 > [ 3.476865] ---[ end trace bae4d98dd36296b7 ]--- So it's a kmemcheck trap while poking sysfs in the middle of the memory kobjects getting created. This code gets run at boot on a *LOT* of systems, so it's probably something specific to your hardware. I'd suspect something like a memory section getting added twice, or a bug in some error handling path. You might want to double-check that all the calls to add_memory_section() look sane. It's also a bummer that kmemcheck doesn't dump out the actual faulting address. -- 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