All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <ryan.underwood@flightsafety.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0.
Date: Thu, 17 Feb 2011 00:17:27 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110217T003826-785@post.gmane.org> (raw)
In-Reply-To: 9F0C2539CB50A743894F8FCEEB1D569206F4A5@mx1.guavus.com

Preeti Khurana <Preeti.Khurana <at> guavus.com> writes:

> 
> I am getting the similar issue as reported
> in https://lkml.org/lkml/2011/2/10/187
> 
> Can someone tell me if the same issue  because I am getting the
> problem on Intel Xeon..
> 

I am seeing exactly the same problem (on 2.6.35 as Preeti reported originally)
on some Xeon servers but only with recently shipped BIOS revisions. The OS is
CentOS 5.5.

In my cases, the system sometimes hangs with no comment, sometimes with a NMI
message immediately before hanging and sometimes with a long trail of
backtrace originating at cpu_idle().  The NMI reason code is different but
in my observation it is usually 21 or 31.

The problem seems to be triggered by accessing a PCI card (via MMIO) because 
until accessing the PCI card, the system will run forever with no problems.

Other servers of exactly the same model (Intel SR2500) but older BIOS revision
are working (working is 3/14/2008, non working is 3/9/2010).  All software is
identical in these cases.

Also, in one instance, kernel v2.6.18 is used on these servers with the
3/14/2008 BIOS revision without a problem.  The rest of the software is again
the same (except for kernel and drivers).

It seems to be a problem with newer kernels combined with the newer Intel BIOS.
I have not tried an older kernel on the newer BIOS yet.

I have not tried the following patches yet which seem to both be for spurious
NMI messages, not accompanied by system lockups:

https://lkml.org/lkml/2011/2/16/106
https://lkml.org/lkml/2011/2/1/286

Both nmi_watchdog=0 and pcie_aspm=off options do not solve the problem.

I am not subscribed so please Cc me.


  reply	other threads:[~2011-02-17  0:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 13:36 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0 Preeti Khurana
2011-02-17  0:17 ` Ryan Underwood [this message]
2011-02-17  7:59   ` Cyrill Gorcunov
2011-02-18  2:40     ` Paul E. McKenney
2011-02-18 20:38       ` Underwood, Ryan
2011-02-21  6:56         ` Preeti Khurana
2011-02-21 16:45           ` Underwood, Ryan
  -- strict thread matches above, loose matches on Subject: below --
2011-02-01 16:27 George Spelvin
2011-02-01 17:52 ` Cyrill Gorcunov
2011-02-01 18:41   ` Don Zickus
2011-02-01 18:44     ` Cyrill Gorcunov
2011-02-01 18:51       ` Don Zickus
2011-02-01 20:00         ` Cyrill Gorcunov
2011-02-02  2:36   ` George Spelvin
2011-02-02  4:18     ` Cyrill Gorcunov
2011-02-16  1:57       ` Dave Airlie
2011-02-16  4:19         ` Cyrill Gorcunov
2011-02-16  8:37           ` Ingo Molnar
2011-02-16  8:49             ` Cyrill Gorcunov
2011-02-16  8:56               ` Ingo Molnar
2011-02-16  9:33                 ` Cyrill Gorcunov
2011-02-16 10:09                   ` Ingo Molnar
2011-02-16 11:08                     ` Cyrill Gorcunov
2011-02-16 11:57         ` George Spelvin
2011-02-17  2:56           ` Dave Airlie
2011-02-17  7:48             ` Cyrill Gorcunov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20110217T003826-785@post.gmane.org \
    --to=ryan.underwood@flightsafety.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.