From: Dave Hansen <dave.hansen@intel.com>
To: Libin <huawei.libin@huawei.com>
Cc: Vegard Nossum <vegardno@ifi.uio.no>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Li Zefan <lizefan@huawei.com>,
guohanjun@huawei.com, zhangdianfang@huawei.com
Subject: Re: [BUG REPORT]kernel panic with kmemcheck config
Date: Tue, 20 Aug 2013 21:46:21 -0700 [thread overview]
Message-ID: <5214461D.9000009@intel.com> (raw)
In-Reply-To: <521429D5.8070003@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] [<ffffffff81046aa7>] ? kmemcheck_trap+0x17/0x30
> [ 3.320507] <<EOE>> <#DB> [<ffffffff8150de8a>] do_debug+0x16a/0x1c0
> [ 3.327029] [<ffffffff8150d815>] debug+0x25/0x40
> [ 3.331714] [<ffffffff812776cc>] ? rb_insert_color+0xcc/0x150
> [ 3.337518] <<EOE>> [<ffffffff811eefd8>] sysfs_link_sibling+0xa8/0xf0
> [ 3.344124] [<ffffffff811ef46a>] ? __sysfs_add_one+0x6a/0x120
> [ 3.349931] [<ffffffff811ef477>] __sysfs_add_one+0x77/0x120
> [ 3.355563] [<ffffffff811ef546>] sysfs_add_one+0x26/0xe0
> [ 3.360937] [<ffffffff811f007c>] create_dir+0x7c/0xd0
> [ 3.366050] [<ffffffff811f0163>] sysfs_create_dir+0x93/0xd0
> [ 3.371684] [<ffffffff81274249>] kobject_add_internal+0xe9/0x270
> [ 3.377748] [<ffffffff81274598>] kobject_add_varg+0x38/0x60
> [ 3.383380] [<ffffffff8127464e>] ? kobject_add+0x1e/0x70
> [ 3.388751] [<ffffffff81274674>] kobject_add+0x44/0x70
> [ 3.393954] [<ffffffff81364f72>] ? device_add+0xc2/0x580
> [ 3.399328] [<ffffffff81364f83>] device_add+0xd3/0x580
> [ 3.404529] [<ffffffff8136455b>] ? device_initialize+0xab/0xc0
> [ 3.410422] [<ffffffff81365449>] device_register+0x19/0x20
> [ 3.415971] [<ffffffff8137abeb>] init_memory_block+0xfb/0x120
> [ 3.421776] [<ffffffff8137aebc>] add_memory_section+0xdc/0x140
> [ 3.427672] [<ffffffff81b33274>] memory_dev_init+0xa3/0xc1
> [ 3.433264] [<ffffffff81b32eef>] driver_init+0x2f/0x31
> [ 3.438466] [<ffffffff81aee7ed>] do_basic_setup+0x29/0xce
> [ 3.443929] [<ffffffff81b0ffd5>] ? sched_init_smp+0x14f/0x156
> [ 3.449735] [<ffffffff81aeea9f>] kernel_init_freeable+0x20d/0x291
> [ 3.455886] [<ffffffff81501330>] ? rest_init+0x80/0x80
> [ 3.461084] [<ffffffff81501339>] kernel_init+0x9/0x180
> [ 3.466285] [<ffffffff8151562c>] ret_from_fork+0x7c/0xb0
> [ 3.471659] [<ffffffff81501330>] ? 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.
next prev parent reply other threads:[~2013-08-21 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 2:44 [BUG REPORT]kernel panic with kmemcheck config Libin
2013-08-20 14:48 ` Dave Hansen
2013-08-21 2:45 ` Libin
2013-08-21 4:46 ` Dave Hansen [this message]
2013-08-22 3:58 ` Libin
2013-08-22 16:45 ` Dave Hansen
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=5214461D.9000009@intel.com \
--to=dave.hansen@intel.com \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=penberg@kernel.org \
--cc=vegardno@ifi.uio.no \
--cc=zhangdianfang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).