From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by kanga.kvack.org (Postfix) with ESMTP id 295A66B0031 for ; Wed, 19 Feb 2014 17:24:44 -0500 (EST) Received: by mail-pd0-f177.google.com with SMTP id x10so941073pdj.8 for ; Wed, 19 Feb 2014 14:24:43 -0800 (PST) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [2607:f8b0:400e:c02::229]) by mx.google.com with ESMTPS id bo2si1000518pbb.313.2014.02.19.14.24.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Feb 2014 14:24:43 -0800 (PST) Received: by mail-pd0-f169.google.com with SMTP id v10so955798pde.0 for ; Wed, 19 Feb 2014 14:24:42 -0800 (PST) Date: Wed, 19 Feb 2014 14:24:41 -0800 (PST) From: David Rientjes Subject: Re: mm: OS boot failed when set command-line kmemcheck=1 In-Reply-To: <53047AE6.4060403@huawei.com> Message-ID: References: <5304558F.9050605@huawei.com> <53047AE6.4060403@huawei.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Xishi Qiu , Robert Richter , Peter Zijlstra , Stephane Eranian , Pekka Enberg Cc: Vegard Nossum , Linux MM , LKML On Wed, 19 Feb 2014, Xishi Qiu wrote: > Here is a warning, I don't whether it is relative to my hardware. > If set "kmemcheck=1 nowatchdog", it can boot. > > code: > ... > pte = kmemcheck_pte_lookup(address); > if (!pte) > return false; > > WARN_ON_ONCE(in_nmi()); > > if (error_code & 2) > ... > > log: > [ 10.920683] WARNING: CPU: 0 PID: 1 at arch/x86/mm/kmemcheck/kmemcheck.c:640 k > memcheck_fault+0xb1/0xc0() > [ 10.920684] Modules linked in: > [ 10.920686] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-rc3-0.1-default+ > #3 > [ 10.920687] Hardware name: Huawei Technologies Co., Ltd. Tecal RH2285 V2-24S/ > BC11SRSC1, BIOS RMISV055 02/02/2013 > [ 10.920690] 0000000000000280 ffff88085f807678 ffffffff814ca491 ffff88085f807 > 6b8 > [ 10.920693] ffffffff8104ce97 0000000000000000 ffff88085f807838 ffff88085f420 > 5d4 > [ 10.920695] 0000000000000000 0000000000000000 ffff88085f4205d4 ffff88085f807 > 6c8 > [ 10.920695] Call Trace: > [ 10.920701] [] dump_stack+0x6a/0x79 > [ 10.920705] [] warn_slowpath_common+0x87/0xb0 > [ 10.920707] [] warn_slowpath_null+0x15/0x20 > [ 10.920710] [] kmemcheck_fault+0xb1/0xc0 > [ 10.920714] [] __do_page_fault+0x39b/0x4c0 > [ 10.920718] [] ? put_dec+0x72/0x90 > [ 10.920720] [] ? number+0x33a/0x360 > [ 10.920723] [] do_page_fault+0x9/0x10 > [ 10.920726] [] page_fault+0x22/0x30 > [ 10.920731] [] ? vt_console_print+0x8c/0x400 > [ 10.920733] [] ? vt_console_print+0x6c/0x400 > [ 10.920737] [] ? msg_print_text+0x18b/0x1f0 > [ 10.920739] [] call_console_drivers+0xc1/0xe0 > [ 10.920741] [] console_unlock+0x236/0x280 > [ 10.920744] [] vprintk_emit+0x2b5/0x450 > [ 10.920746] [] ? kmemcheck_fault+0xb1/0xc0 > [ 10.920748] [] printk+0x4a/0x4c > [ 10.920750] [] ? kmemcheck_fault+0xb1/0xc0 > [ 10.920753] [] warn_slowpath_common+0x3e/0xb0 > [ 10.920755] [] warn_slowpath_null+0x15/0x20 > [ 10.920757] [] kmemcheck_fault+0xb1/0xc0 > [ 10.920760] [] __do_page_fault+0x39b/0x4c0 > [ 10.920763] [] do_page_fault+0x9/0x10 > [ 10.920765] [] page_fault+0x22/0x30 > [ 10.920769] [] ? x86_perf_event_update+0x2/0x70 > [ 10.920772] [] ? intel_pmu_save_and_restart+0x11/0x50 > [ 10.920774] [] intel_pmu_handle_irq+0x142/0x3a0 > [ 10.920777] [] perf_event_nmi_handler+0x35/0x60 > [ 10.920779] [] nmi_handle+0x63/0x150 > [ 10.920782] [] default_do_nmi+0x63/0x290 > [ 10.920784] [] do_nmi+0xa8/0xe0 > [ 10.920786] [] end_repeat_nmi+0x1e/0x2e > [ 10.920789] [] ? retint_signal+0x78/0x78 > [ 10.920791] [] ? retint_signal+0x78/0x78 > [ 10.920793] [] ? retint_signal+0x78/0x78 > [ 10.920799] <> <#DB> [] ? acpi_ns_walk_namespace+0x > 98/0x251 > I added some perf events and kmemcheck people to the cc list. This appears to happen during an NMI when faulting in struct perf_sample_data data. -- 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