From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754704Ab3AaNG5 (ORCPT ); Thu, 31 Jan 2013 08:06:57 -0500 Received: from hydra.sisk.pl ([212.160.235.94]:36117 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754336Ab3AaNGr (ORCPT ); Thu, 31 Jan 2013 08:06:47 -0500 From: "Rafael J. Wysocki" To: Jiri Slaby , Borislav Petkov Cc: Bjorn Helgaas , x86@kernel.org, lkml , Konstantin Khlebnikov Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. Date: Thu, 31 Jan 2013 14:12:58 +0100 Message-ID: <3066730.6MVSAfNyye@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.8.0-rc5; KDE/4.9.5; x86_64; ; ) In-Reply-To: <510A27C8.3070909@suse.cz> References: <20130129202848.GE25415@pd.tnic> <20130131070926.GC4926@pd.tnic> <510A27C8.3070909@suse.cz> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, January 31, 2013 09:14:00 AM Jiri Slaby wrote: > On 01/31/2013 08:09 AM, Borislav Petkov wrote: > > On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: > >> On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: > >>> On 01/31/2013 12:12 AM, Jiri Slaby wrote: > >>>> I think I will start with commenting parts of `power' script to see > >>>> exactly which of the power savings cause this. > >>> > >>> ... NMI watchdog. If I remove it from the script, the problem > >>> disappears. If I try it alone, I have those NMIs. > >> > >> Well, beats me. :-( > >> > >> I suspect that it doesn't quiesce itself sufficiently before image restoration > >> and we get some crosstalk between the boot kernel and the image kernel. > > > > Well, I did what Jiri said causes it: > > > > echo 0 > /proc/sys/kernel/nmi_watchdog > > > > No NMI. > > > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > > to "Good", then suspend to disk, when I resume I get the NMI and this > > time the unknown reason is 0x3c. Sounds like this needs bisection... > > Btw, this is latest -rc5 + tip/master and Jiri triggers it on 3.7-stable > > ... > > And 3.6(.0) was the first one I _tried_ and had that issue too. Not sure > if there is any bisect-good kernel to start with. > > > Btw, this e1000e thing has another problem: when I unplug the network > > cable and replug it again, it cannot ping local network anymore. > > Normally, when you plug the network cable back in, it does some sort if > > link detection saying eth link is back up but it doesn't say it on that > > box - only a reboot fixes it. Hmm. > > I think this is what Konstantin fixes with his patches. Yes, there are two bugs in e1000e, it appears. Konstantin's patch [2/5] fixes one of them, but the other one has to be fixed differently. Boris, would you be able to test a couple of e1000e patches for me? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.