From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751595Ab3CAMzk (ORCPT ); Fri, 1 Mar 2013 07:55:40 -0500 Received: from mail-ee0-f49.google.com ([74.125.83.49]:37372 "EHLO mail-ee0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751462Ab3CAMzj (ORCPT ); Fri, 1 Mar 2013 07:55:39 -0500 Message-ID: <5130A55E.8030508@suse.cz> Date: Fri, 01 Mar 2013 13:55:58 +0100 From: Jiri Slaby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20130124 Thunderbird/19.0 MIME-Version: 1.0 To: Borislav Petkov , "Rafael J. Wysocki" , Bjorn Helgaas , x86@kernel.org, lkml , Konstantin Khlebnikov Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. References: <20130129202848.GE25415@pd.tnic> <5109A8F1.9040707@suse.cz> <5109B11C.2010400@suse.cz> <5170962.qHnbnlVDfx@vostro.rjw.lan> <20130131070926.GC4926@pd.tnic> <510A2B1C.1060108@suse.cz> <20130131131805.GG4926@pd.tnic> <20130131132400.GH4926@pd.tnic> In-Reply-To: <20130131132400.GH4926@pd.tnic> X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/31/2013 02:24 PM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 02:18:05PM +0100, Borislav Petkov wrote: >>> And if I pass nmi_watchdog=0 to the image kernel, it should be gone I >>> guess. >> >> How do you pass options the image kernel? > > Yep, passing "nmi_watchdog=0" to the kernel (both when you boot and > when you resume) fixes the issue - no more unknown NMIs. Did only 3 s/r > cycles though. FWIW the last time I saw the unhandled NMI was on 31st Jan. Since I disabled NMI watchdog no more unhandled NMIs. I have to add that I don't use ethernet at all. -- js suse labs