From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ryan Underwood <ryan.underwood@flightsafety.com>,
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 18:40:55 -0800 [thread overview]
Message-ID: <20110218024055.GA2237@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTikEMOxtTe7afmYsvyQkJi7j70TRX3cPPR0X=uQj@mail.gmail.com>
On Thu, Feb 17, 2011 at 10:59:43AM +0300, Cyrill Gorcunov wrote:
> On Thu, Feb 17, 2011 at 3:17 AM, Ryan Underwood
> <ryan.underwood@flightsafety.com> wrote:
> > 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.
> >
> ...
> > 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.
Given 2.6.35, has anyone tried applying the following patch?
https://patchwork.kernel.org/patch/23985/
It turned out to resolve an otherwise mysterious RCU CPU stall warning
for someone running 2.6.36, IIRC.
Thanx, Paul
next prev parent reply other threads:[~2011-02-18 16:16 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
2011-02-17 7:59 ` Cyrill Gorcunov
2011-02-18 2:40 ` Paul E. McKenney [this message]
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=20110218024055.GA2237@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan.underwood@flightsafety.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox