From: Gleb Natapov <gleb@redhat.com>
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Cc: kvm@vger.kernel.org
Subject: Re: kernel 3.10.1 - "NMI received for unknown reason"
Date: Tue, 30 Jul 2013 08:31:34 +0300 [thread overview]
Message-ID: <20130730053134.GG28372@redhat.com> (raw)
In-Reply-To: <51F6D578.5030105@sp.consulting.lsexperts.de>
On Mon, Jul 29, 2013 at 10:50:00PM +0200, Stefan Pietsch wrote:
> On 29.07.2013 11:16, Gleb Natapov wrote:
> > On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote:
> >> On 26.07.2013 20:39, Gleb Natapov wrote:
> >>> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
> >>>> Hi all,
> >>>>
> >>>> starting a virtual machine (Debian sid) with KVM on my host running
> >>>> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
> >>>>
> >>> Are those messages printed by a host or a guest?
> >>
> >> The host shows the messages.
> >>
> >>>> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >>>> [ 765.522927] Do you have a strange power saving mode enabled?
> >>>> [ 765.522930] Dazed and confused, but trying to continue
> >>>> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
> >>>> [ 770.487740] Do you have a strange power saving mode enabled?
> >>>> [ 770.487742] Dazed and confused, but trying to continue
> >>>> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
> >>>> [ 846.340973] Do you have a strange power saving mode enabled?
> >>>> [ 846.340976] Dazed and confused, but trying to continue
> >>>> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >>>> [ 847.563029] Do you have a strange power saving mode enabled?
> >>>> [ 847.563032] Dazed and confused, but trying to continue
> >>
> >> Is it safe to ignore them?
> >>
> > They should not happen. What is the last kernel version you tried that
> > does not produce them? Can you verify that they do not happen without
> > guest running? What is the qemu command line you are using to start the
> > guest and what "cat /proc/cpuinfo" looks like in the guest?
>
> The Debian wheezy kernel (3.2.46) does not show this behaviour.
> It is directly related to KVM and I found out that replacing the option
> "-cpu coreduo" with "-cpu kvm32" does not generate the NMI messages.
>
What happen if you run perf on your host (perf record -a)?
Do you see same NMI messages?
--
Gleb.
next prev parent reply other threads:[~2013-07-30 5:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 18:25 kernel 3.10.1 - "NMI received for unknown reason" Stefan Pietsch
2013-07-26 18:39 ` Gleb Natapov
2013-07-29 9:09 ` Stefan Pietsch
2013-07-29 9:16 ` Gleb Natapov
2013-07-29 20:50 ` Stefan Pietsch
2013-07-30 5:31 ` Gleb Natapov [this message]
2013-07-31 9:10 ` Stefan Pietsch
2013-07-31 9:20 ` Gleb Natapov
2013-08-02 6:24 ` Stefan Pietsch
2013-08-04 12:44 ` Gleb Natapov
2013-08-09 19:14 ` Stefan Pietsch
2013-08-25 11:45 ` Gleb Natapov
2013-08-26 21:48 ` Stefan Pietsch
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=20130730053134.GG28372@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=stefan.pietsch@lsexperts.de \
/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.