From: Jiri Slaby <jslaby@suse.cz>
To: Borislav Petkov <bp@alien8.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
Konstantin Khlebnikov <khlebnikov@openvz.org>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Date: Thu, 04 Apr 2013 11:38:21 +0200 [thread overview]
Message-ID: <515D4A0D.7070302@suse.cz> (raw)
In-Reply-To: <20130404093302.GB32271@pd.tnic>
On 04/04/2013 11:33 AM, Borislav Petkov wrote:
> On Thu, Apr 04, 2013 at 09:32:09AM +0200, Jiri Slaby wrote:
>> And yesterday I plugged in an ethernet cable for a wihle and guess
>> what happened today: Uhhuh. NMI received for unknown reason 2c on CPU
>> 0.
>>
>> Still holds that this is the first time since Jan.
>
> Yeah, you could try my sure-fire way to trigger it:
>
> * boot the box without any "nmi_watchdog" tweaks on the kernel cmdline -
> i.e. it should be enabled.
>
> * turn off NMI watchdog through powertop or directly through
> /proc/sys/kernel/nmi_watchdog
>
> * suspend to disk
>
> Now when you resume, you should either see unknown reason 2c or 3c.
Oh, this reminds me that this time it might be unrelated to yesterday's
use of ethernet. Because today, I resumed the system by a kernel which I
didn't pass nmi_watchdog=0 to.
Hmm. So you can silently ignore the report I sent today :).
And sure, the way you describe above "works" for me to trigger the
issue... I just wanted to note the ethernet may interfere.
Anyway, I will bake some hack to disable NMI before jumping to the
resumed kernel and will see what happens...
--
js
suse labs
next prev parent reply other threads:[~2013-04-04 9:38 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 20:28 Uhhuh. NMI received for unknown reason 2c on CPU 0 Borislav Petkov
2013-01-29 21:32 ` Bjorn Helgaas
2013-01-30 3:42 ` Borislav Petkov
2013-01-30 17:27 ` Bjorn Helgaas
2013-01-30 17:44 ` Borislav Petkov
2013-01-30 19:43 ` Jiri Slaby
2013-01-30 20:00 ` Borislav Petkov
2013-01-30 20:33 ` Jiri Slaby
2013-01-30 21:39 ` Rafael J. Wysocki
2013-01-30 22:17 ` Jiri Slaby
2013-01-30 22:45 ` Rafael J. Wysocki
2013-01-30 23:12 ` Jiri Slaby
2013-01-30 23:47 ` Jiri Slaby
2013-01-31 0:54 ` Rafael J. Wysocki
2013-01-31 7:09 ` Borislav Petkov
2013-01-31 8:14 ` Jiri Slaby
2013-01-31 13:12 ` Rafael J. Wysocki
2013-01-31 13:10 ` Borislav Petkov
2013-02-02 23:04 ` Rafael J. Wysocki
2013-02-03 14:46 ` Borislav Petkov
2013-02-03 20:15 ` Rafael J. Wysocki
2013-02-03 20:58 ` Borislav Petkov
2013-02-03 21:06 ` Borislav Petkov
2013-02-03 21:15 ` Borislav Petkov
2013-02-14 14:39 ` Borislav Petkov
2013-02-14 17:17 ` Bjorn Helgaas
2013-02-14 19:12 ` Borislav Petkov
2013-02-15 8:54 ` Konstantin Khlebnikov
2013-02-15 9:16 ` Borislav Petkov
2013-03-04 21:50 ` Borislav Petkov
2013-03-05 0:16 ` Bjorn Helgaas
2013-03-05 9:42 ` Jiri Slaby
2013-03-05 9:58 ` Borislav Petkov
2013-03-05 10:01 ` Jiri Slaby
2013-03-05 10:02 ` Jeff Kirsher
2013-03-05 10:14 ` Borislav Petkov
2013-03-05 10:29 ` Jeff Kirsher
2013-03-05 11:27 ` Borislav Petkov
2013-03-05 11:33 ` Jeff Kirsher
2013-03-05 11:42 ` Borislav Petkov
2013-03-06 0:13 ` Rafael J. Wysocki
2013-03-06 0:19 ` Borislav Petkov
2013-03-08 16:47 ` Borislav Petkov
2013-03-05 10:01 ` Jeff Kirsher
2013-03-05 10:04 ` Jiri Slaby
2013-03-01 12:51 ` e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] Jiri Slaby
2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 Jiri Slaby
2013-02-06 21:29 ` Rafael J. Wysocki
2013-01-31 8:28 ` Jiri Slaby
2013-01-31 13:18 ` Borislav Petkov
2013-01-31 13:24 ` Borislav Petkov
2013-03-01 12:55 ` Jiri Slaby
2013-04-04 7:32 ` Jiri Slaby
2013-04-04 9:33 ` Borislav Petkov
2013-04-04 9:38 ` Jiri Slaby [this message]
2013-04-04 9:58 ` Borislav Petkov
2013-01-31 13:29 ` Rafael J. Wysocki
2013-02-03 21:29 ` Jiri Slaby
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=515D4A0D.7070302@suse.cz \
--to=jslaby@suse.cz \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).