From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>, Abel Gordon <ABELG@il.ibm.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-owner@vger.kernel.org" <kvm-owner@vger.kernel.org>
Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.
Date: Mon, 13 May 2013 08:31:33 +0200 [thread overview]
Message-ID: <519088C5.8050703@siemens.com> (raw)
In-Reply-To: <CAOaxAcZHrPT+bmn2bCemSL5qppiAhCRY8kuwtfXELQdn9_iMHA@mail.gmail.com>
On 2013-05-12 18:52, Kashyap Chamarthy wrote:
>>> --------------------
>>> ....
>>> [ 217.938034] Uhhuh. NMI received for unknown reason 30 on CPU 0.
>>> [ 217.938034] Do you have a strange power saving mode enabled?
>>> .[ 222.523373] Uhhuh. NMI received for unknown reason 20 on CPU 0.
>>> [ 222.524073] Do you have a strange power saving mode enabled?
>>> [ 222.524073] Dazed and confused, but trying to continue
>>> [ 243.860319] Uhhuh. NMI received for unknown reason 30 on CPU 0
>>> .....
>>> --------------------
>>> At the moment, L2 guest creation stuck at the above message
>>>
>> Are those in L2 dmesg or L1?
>
> L2 dmesg.
>
>
>>> $ cat /etc/grub2.cfg | egrep -i 'hpet|nmi'
>>>
>> IIRC watchdog is enabled by default.
>
> Indeed, you're right. I disabled NMI on L1, and rebooted the newly
> created L2 guest starts just fine.
NMI watchdogs go via some perf counters theses days IIRC. Can anyone
tell me which of those may be used in Kashyap's setup? I'm probably
lacking them for my guests and therefore do not see the errors.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-05-13 6:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 13:00 [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted Kashyap Chamarthy
[not found] ` <CAOaxAcZ1uyx-RrmDEiZhG2H8H5zTCK9iz1nHJKEJwUfhn=vZHA@mail.gmail.com>
2013-05-10 14:41 ` Kashyap Chamarthy
2013-05-10 15:12 ` Jan Kiszka
2013-05-10 15:24 ` Jan Kiszka
2013-05-10 15:39 ` Kashyap Chamarthy
2013-05-10 15:46 ` Kashyap Chamarthy
2013-05-10 16:33 ` Jan Kiszka
2013-05-10 17:40 ` Nakajima, Jun
2013-05-10 18:09 ` Jan Kiszka
2013-05-10 21:37 ` Kashyap Chamarthy
2013-05-11 6:55 ` Kashyap Chamarthy
2013-05-12 8:32 ` Gleb Natapov
2013-05-12 12:30 ` Kashyap Chamarthy
2013-05-12 12:38 ` Gleb Natapov
2013-05-12 12:42 ` Kashyap Chamarthy
2013-05-12 12:59 ` Abel Gordon
2013-05-12 13:06 ` Kashyap Chamarthy
2013-05-12 13:31 ` Kashyap Chamarthy
2013-05-12 13:33 ` Kashyap Chamarthy
2013-05-12 15:52 ` Gleb Natapov
2013-05-12 16:52 ` Kashyap Chamarthy
2013-05-13 6:31 ` Jan Kiszka [this message]
2013-05-13 6:39 ` Gleb Natapov
2013-05-13 6:45 ` Ren, Yongjie
2013-05-13 6:57 ` Jan Kiszka
2013-05-13 7:06 ` Gleb Natapov
2013-05-12 13:48 ` Abel Gordon
2013-05-12 15:35 ` Gleb Natapov
2013-05-12 16:29 ` Kashyap Chamarthy
2013-05-10 21:37 ` Kashyap Chamarthy
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=519088C5.8050703@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ABELG@il.ibm.com \
--cc=gleb@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=kashyap.cv@gmail.com \
--cc=kvm-owner@vger.kernel.org \
--cc=kvm@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 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.