Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756864Ab1CAQnE (ORCPT ); Tue, 1 Mar 2011 11:43:04 -0500 Received: from hosting.visp.net.lb ([194.146.153.11]:45883 "EHLO hosting.visp.net.lb" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756567Ab1CAQnD (ORCPT ); Tue, 1 Mar 2011 11:43:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 01 Mar 2011 18:42:46 +0200 From: denys@visp.net.lb To: Cyrill Gorcunov Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , , Subject: Re: NMI received for unknown reason, 2.6.38-rc6 =?UTF-8?Q?regression=3F?= In-Reply-To: <4D6D1A0B.3050903@gmail.com> References: <950d04b27ce43565cdef24e4072d7e71@visp.net.lb> <4D6D1A0B.3050903@gmail.com> Message-ID: <9f4d7fae5845b91debc86a65d51bf96a@visp.net.lb> User-Agent: VISP Webmail/0.5-beta Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2052 Lines: 46 On Tue, 01 Mar 2011 19:08:43 +0300, Cyrill Gorcunov wrote: > On 03/01/2011 06:03 PM, denys@visp.net.lb wrote: >> I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on >> many of them error/warining, flooding kernel log. Here is short >> snapshot: >> >> [ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> [ 1882.057576] Do you have a strange power saving mode enabled? >> [ 1882.057672] Dazed and confused, but trying to continue >> [ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> [ 2421.419835] Do you have a strange power saving mode enabled? >> [ 2421.419930] Dazed and confused, but trying to continue >> [ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. >> [ 2636.016934] Do you have a strange power saving mode enabled? >> [ 2636.017003] Dazed and confused, but trying to continue >> >> Full dmesg from 2 machines: >> http://www.nuclearcat.com/dmesg1.txt >> http://www.nuclearcat.com/dmesg2.txt >> I can provide more, if required. >> >> It seems nmi_watchdog is enabled by default, and it is causing >> issue. I am checking now with nmi_watchdog=0, but i need more time to >> confirm that. >> Also i am experiencing some problem with ppp users(all of them is >> pppoe servers), but i am not sure it is related to that, so maybe this >> NMI warning is just cosmetic regression. >> >> All systems is x86, same kernel config. >> If you need more information - let me know. >> > > nmi_watchdog=0 should help here, actually a nit was fixed by > https://patchwork.kernel.org/patch/566611/ > which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or > final .38. If you have an ability > to pickup it and test -- this would be great! I test it, and it seems helps. At least on one host, and yes, seems all of them P4. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/