linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 07:48:09 -0700	[thread overview]
Message-ID: <521381A9.4020501@intel.com> (raw)
In-Reply-To: <5212D7F2.3020308@huawei.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 717 bytes --]

On 08/19/2013 07:44 PM, Libin wrote:
> When kmemcheck kernel support configuredGBP!we encountered random kernel panic
> (sometimes can be booted) during system boot process in our environment. I
> have tested the mainline kernel version from v3.0 to v3.11-rc6, they also
> have this problem. And the memory limit within 4G also tested.

Could you provide a more complete oops?  Doing it properly usually
requires either a remote console of some kind (netconsole, serial, usb
debug, etc...).

--
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>

  parent reply	other threads:[~2013-08-20 14:48 UTC|newest]

Thread overview: 8+ 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  2:55 ` Wanpeng Li
2013-08-20  2:55 ` Wanpeng Li
2013-08-20 14:48 ` Dave Hansen [this message]
2013-08-21  2:45   ` Libin
2013-08-21  4:46     ` Dave Hansen
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=521381A9.4020501@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).