Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758416Ab1BPI4X (ORCPT ); Wed, 16 Feb 2011 03:56:23 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:53178 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750877Ab1BPI4U (ORCPT ); Wed, 16 Feb 2011 03:56:20 -0500 Date: Wed, 16 Feb 2011 09:56:05 +0100 From: Ingo Molnar To: Cyrill Gorcunov Cc: Dave Airlie , George Spelvin , a.p.zijlstra@chello.nl, dzickus@redhat.com, eranian@google.com, linux-kernel@vger.kernel.org, ming.m.lin@intel.com Subject: Re: 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0. Message-ID: <20110216085605.GA18842@elte.hu> References: <4D484853.9020409@gmail.com> <20110202023610.3799.qmail@science.horizon.com> <20110216083747.GF16529@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1887 Lines: 57 * Cyrill Gorcunov wrote: > On Wed, Feb 16, 2011 at 11:37 AM, Ingo Molnar wrote: > ... > >> >> > >> > > >> > Ping on this problem, still seeing > >> > > >> > Uhhuh. NMI received for unknown reason 3c on CPU 0. > >> > Do you have a strange power saving mode enabled? > >> > Dazed and confused, but trying to continue > >> > > >> > on my Pentium-D system here with latest Linus head. > >> > > >> > its sometimes 3c, sometimes 3d, I'm going to bisect and push for > >> > reverts if nobody still has any clue about how to fix this. > >> > > >> > Dave. > >> > > >> > >> We still trying to resolve it but without success yet. There is no > >> easy way to revert it. One of the option might be to disable perf on > >> p4 for a while. If this is acceptable -- i'll cook such patch and send > >> it to Ingo. Hm? > > > > That's not really acceptable - need to fix it or revert it to the last working > > state. Which commit broke it? > > > > Thanks, > > > > ? ? ? ?Ingo > > > > I can't say you the commit id after which unknown-nmi start happening > (i'm out of git tree > at moment) but even then this commit should not be reverted since the > problem is in > p4 code not in the rest of perf system. > > I have two patches here (attached) and would really appreciate of > their testing on HT machine > together with kgdb bootup tests enabled. Dave could you please? Could these patches fix Dave's non-kgdb problem? Dave isnt using kgdb but is probably using perf which triggers NMIs? Dave, can you confirm that? And it's a spurious NMI message, not actual lockup or other misbehavior, right? Thanks, Ingo -- 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/