From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Avi Kivity <avi@redhat.com>,
mtosatti@redhat.com, xiaoguangrong@linux.vnet.ibm.com,
mst@redhat.com, alex.williamson@redhat.com,
"p.her >> Philipp Herz - Profihost AG" <p.herz@profihost.ag>
Subject: kernel 3.8.9 call trace kvm Watchdog detected hard LOCKUP
Date: Tue, 07 May 2013 13:59:02 +0200 [thread overview]
Message-ID: <5188EC86.4050106@profihost.ag> (raw)
Hello list,
today i kvm host crashed running vanilla kernel 3.8.9.
The call trace looks like this:
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 18
Pid: 29053, comm: kvm Tainted: G O 3.8.9+16-ph #1
Call Trace:
<NMI> [<ffffffff8150a86b>] panic+0xbf/0x1df
[<ffffffff8100ae73>] ? native_sched_clock+0x13/0x80
[<ffffffff810b40c1>] watchdog_overflow_callback+0xb1/0xc0
[<ffffffff810e103c>] __perf_event_overflow+0x9c/0x220
[<ffffffff81013878>] ? x86_perf_event_set_period+0xd8/0x160
[<ffffffff810e18e4>] perf_event_overflow+0x14/0x20
[<ffffffff81019a9c>] intel_pmu_handle_irq+0x1bc/0x330
[<ffffffff8131feac>] ? ghes_read_estatus+0xac/0x170
[<ffffffff81012991>] perf_event_nmi_handler+0x21/0x30
[<ffffffff810061ca>] nmi_handle+0x5a/0x80
[<ffffffff81006333>] default_do_nmi+0x63/0x200
[<ffffffff81006560>] do_nmi+0x90/0xd0
[<ffffffff8150dff1>] end_repeat_nmi+0x1e/0x2e
[<ffffffff8150d765>] ? _raw_spin_lock+0x25/0x30
[<ffffffff8150d765>] ? _raw_spin_lock+0x25/0x30
[<ffffffff8150d765>] ? _raw_spin_lock+0x25/0x30
<<EOE>> [<ffffffffa015b22f>] kvm_guest_time_update+0x5f/0x310 [kvm]
[<ffffffffa023c03d>] ? vmx_set_cr3+0x9d/0x130 [kvm_intel]
[<ffffffffa023a7ca>] ? vmx_save_host_state+0xea/0x1a0 [kvm_intel]
[<ffffffffa015b92f>] vcpu_enter_guest+0x13f/0x770 [kvm]
[<ffffffffa015c100>] __vcpu_run+0x1a0/0x320 [kvm]
[<ffffffffa015c311>] kvm_arch_vcpu_ioctl_run+0x91/0x1f0 [kvm]
[<ffffffffa0147efe>] kvm_vcpu_ioctl+0x38e/0x550 [kvm]
[<ffffffff810987e0>] ? futex_wake+0x110/0x120
[<ffffffff81153d9b>] do_vfs_ioctl+0x7b/0x380
[<ffffffff8109a6c6>] ? sys_futex+0x76/0x170
[<ffffffff811540f2>] sys_ioctl+0x52/0x80
[<ffffffff810603b1>] ? do_sigpending+0xa1/0xc0
[<ffffffff8150e229>] system_call_fastpath+0x16/0x1b
Shutting down cpus with NMI
Has anybody seen this and know a fix?
Thanks!
Stefan
reply other threads:[~2013-05-07 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5188EC86.4050106@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=p.herz@profihost.ag \
--cc=xiaoguangrong@linux.vnet.ibm.com \
/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.