From: Preeti Khurana <Preeti.Khurana@guavus.com>
To: "Underwood, Ryan" <Ryan.Underwood@flightsafety.com>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
Cyrill Gorcunov <gorcunov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0.
Date: Mon, 21 Feb 2011 06:56:44 +0000 [thread overview]
Message-ID: <9F0C2539CB50A743894F8FCEEB1D56920714B3@mx1.guavus.com> (raw)
In-Reply-To: <4FE5E7F6EBBC274ABEE8E2DDB69E6DBF33970A4AF0@srv060ex01.ssd.fsi.com>
> >
> > 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.
> >
>
This fix is already in 2.6.35, so this doesn't seem to be an issue.
> Now I've tried 2.6.38-rc5 which already includes that patch, and the same
> problems remain. It also includes the following patch that Preeti seems to
> have had some success with on 2.6.35, so my problem must really be
> elsewhere:
> https://lkml.org/lkml/2011/1/6/131
>
> Since a previous BIOS version is known to work I may end up having to do
> some BIOS-bisecting today...
Ryan,
Cant say that this patch (https://lkml.org/lkml/2011/1/6/131) worked for me since I am not able to reproduce the problem quite reliably and now not getting the problem even under the original kernel without this patch. Just wondering what triggers this problem.
next prev parent reply other threads:[~2011-02-21 7:01 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
2011-02-18 20:38 ` Underwood, Ryan
2011-02-21 6:56 ` Preeti Khurana [this message]
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=9F0C2539CB50A743894F8FCEEB1D56920714B3@mx1.guavus.com \
--to=preeti.khurana@guavus.com \
--cc=Ryan.Underwood@flightsafety.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 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.