From: Ingo Molnar <mingo@elte.hu>
To: denys@visp.net.lb
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NMI received for unknown reason, 2.6.38-rc6 regression?
Date: Wed, 2 Mar 2011 08:59:31 +0100 [thread overview]
Message-ID: <20110302075931.GD15665@elte.hu> (raw)
In-Reply-To: <9f4d7fae5845b91debc86a65d51bf96a@visp.net.lb>
* denys@visp.net.lb <denys@visp.net.lb> wrote:
> On Tue, 01 Mar 2011 19:08:43 +0300, Cyrill Gorcunov wrote:
> >On 03/01/2011 06:03 PM, denys@visp.net.lb wrote:
> >>I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on
> >>many of them error/warining, flooding kernel log. Here is short
> >>snapshot:
> >>
> >>[ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0.
> >>[ 1882.057576] Do you have a strange power saving mode enabled?
> >>[ 1882.057672] Dazed and confused, but trying to continue
> >>[ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0.
> >>[ 2421.419835] Do you have a strange power saving mode enabled?
> >>[ 2421.419930] Dazed and confused, but trying to continue
> >>[ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1.
> >>[ 2636.016934] Do you have a strange power saving mode enabled?
> >>[ 2636.017003] Dazed and confused, but trying to continue
> >>
> >>Full dmesg from 2 machines:
> >>http://www.nuclearcat.com/dmesg1.txt
> >>http://www.nuclearcat.com/dmesg2.txt
> >>I can provide more, if required.
> >>
> >>It seems nmi_watchdog is enabled by default, and it is causing
> >>issue. I am checking now with nmi_watchdog=0, but i need more
> >>time to confirm that.
> >>Also i am experiencing some problem with ppp users(all of them
> >>is pppoe servers), but i am not sure it is related to that, so
> >>maybe this NMI warning is just cosmetic regression.
> >>
> >>All systems is x86, same kernel config.
> >>If you need more information - let me know.
> >>
> >
> >nmi_watchdog=0 should help here, actually a nit was fixed by
> >https://patchwork.kernel.org/patch/566611/
> >which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or
> >final .38. If you have an ability
> >to pickup it and test -- this would be great!
> I test it, and it seems helps. At least on one host, and yes, seems
> all of them P4.
Mind checking -rc7, does it work 'out of box', without requiring any workarounds?
-rc7 already has this fix included:
7d44ec193d95: perf, x86: P4 PMU: Fix spurious NMI messages
-rc6 did not have it yet.
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-02 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 15:03 NMI received for unknown reason, 2.6.38-rc6 regression? denys
2011-03-01 16:08 ` Cyrill Gorcunov
2011-03-01 16:42 ` denys
2011-03-01 17:03 ` Cyrill Gorcunov
2011-03-02 7:59 ` Ingo Molnar [this message]
2011-03-02 13:16 ` denys
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=20110302075931.GD15665@elte.hu \
--to=mingo@elte.hu \
--cc=denys@visp.net.lb \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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.