linux-kernel - Re: [BUG REPORT]kernel panic with kmemcheck config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <521429D5.8070003@huawei.com>
Date:	Wed, 21 Aug 2013 10:45:41 +0800
From:	Libin <huawei.libin@...wei.com>
To:	Dave Hansen <dave.hansen@...el.com>
CC:	Vegard Nossum <vegardno@....uio.no>,
	Pekka Enberg <penberg@...nel.org>, <linux-mm@...ck.org>,
	<linux-kernel@...r.kernel.org>, Li Zefan <lizefan@...wei.com>,
	<guohanjun@...wei.com>, <zhangdianfang@...wei.com>
Subject: Re: [BUG REPORT]kernel panic with kmemcheck config

On 2013/8/20 22:48, Dave Hansen wrote:
> On 08/19/2013 07:44 PM, Libin wrote:
>> When kmemcheck kernel support configured，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...).
> 

Thanks for your suggestion, here are two detailed crash information
with mainline 3.11-rc6 kernel version, in our environment described
previously.

Thanks,
Libin


> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
> 
> 



Download attachment "log_21093441.log" of type "application/octet-stream" (28639 bytes)

View attachment "log_21094434.log" of type "text/plain" (47169 bytes)