From: Jiri Slaby <jirislaby@gmail.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Francis Moreau <francis.moro@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: v3.0: Weird kernel log message when resuming avout NMI received
Date: Sun, 31 Jul 2011 13:19:29 +0200 [thread overview]
Message-ID: <4E353A41.2010405@gmail.com> (raw)
In-Reply-To: <20110731110641.GG2209@sun>
On 07/31/2011 01:06 PM, Cyrill Gorcunov wrote:
> On Sun, Jul 31, 2011 at 08:56:30AM +0200, Francis Moreau wrote:
>> Hello,
>>
>> I'm seeing those kernel message when resuming:
>>
>> [ 524.973283] Uhhuh. NMI received for unknown reason 3d on CPU 0.
>> [ 524.973288] Do you have a strange power saving mode enabled?
>> [ 524.973289] Dazed and confused, but trying to continue
>>
>> I don't know if it's important or not because the system seems to work
>> after but maybe it worths to report
>>
>
> Hi Francis, cpu please?
Hi, I'm seeing those too. For a longer time though. Please see
https://bugzilla.novell.com/show_bug.cgi?id=678882#c16
I suspect NMI watchdog rewrite caused this.
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
cpu MHz : 2993.060
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts
tpr_shadow vnmi flexpriority
bogomips : 5986.12
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
cpu MHz : 2993.060
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts
tpr_shadow vnmi flexpriority
bogomips : 5984.98
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
thanks,
--
js
next prev parent reply other threads:[~2011-07-31 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 6:56 v3.0: Weird kernel log message when resuming avout NMI received Francis Moreau
2011-07-31 11:06 ` Cyrill Gorcunov
2011-07-31 11:19 ` Jiri Slaby [this message]
2011-07-31 11:26 ` Cyrill Gorcunov
2011-08-02 19:48 ` Don Zickus
2011-08-02 21:00 ` Jiri Slaby
2011-08-03 0:52 ` Donald Zickus II
2011-07-31 15:20 ` Francis Moreau
2011-07-31 15:32 ` Cyrill Gorcunov
2011-08-01 11:05 ` Peter Zijlstra
2011-08-01 11:21 ` Cyrill Gorcunov
2011-08-01 12:12 ` Peter Zijlstra
2011-08-15 8:37 ` Francis Moreau
2011-08-16 15:07 ` Francis Moreau
2011-08-02 19:52 ` Don Zickus
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=4E353A41.2010405@gmail.com \
--to=jirislaby@gmail.com \
--cc=francis.moro@gmail.com \
--cc=gorcunov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox