From: Kasper Sandberg <lkml@metanurb.dk>
To: kvm@vger.kernel.org
Subject: kvm kernel backtrace 2.6.27.3 using kvm 78 userspace
Date: Sat, 22 Nov 2008 21:49:34 +0100 [thread overview]
Message-ID: <1227386974.19624.103.camel@localhost> (raw)
Hello.
I just noticed that my dmesg had been flooded with backtraces, appearing
to be of KVM origin. I realize that my kernel is tainted, and slightly
outdated, however, i just wanted to drop the log here in case it might
be useful, but feel free to completely ignore it :)
i am not subscribed to the kvm list, so please cc me in case you need
further info..
my entire dmesg was flooded with backtraces looking practically
identical to this one, so i will only paste a few of them, however,
should you want more(though from a quick look they appear identical), i
can put online the complete log
kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9
------------[ cut here ]------------
WARNING: at arch/x86/kvm/x86.c:185 kvm_queue_exception_e+0x63/0x70
[kvm]()
Modules linked in: tun ext3 jbd mbcache usb_storage cryptomgr cbc
aes_x86_64 aes_generic dm_crypt dm_mod crypto_blkcipher sha256_generic
crypto_algapi coretemp it87 hwmon_vid hwmon snd_seq kvm_intel kvm fuse
nvidia(P) snd_usb_audio snd_hda_intel snd_usb_lib snd_rawmidi
snd_seq_device snd_pcm snd_timer snd_hwdep psmouse thermal ehci_hcd rtc
snd ohci1394 ieee1394 soundcore i2c_core processor snd_page_alloc r8169
button
Pid: 20168, comm: kvm Tainted: P W 2.6.27.3 #1
Call Trace:
[<ffffffff80235c84>] warn_on_slowpath+0x64/0xb0
[<ffffffffa0899c01>] paging64_gva_to_gpa+0x21/0x50 [kvm]
[<ffffffffa088cc09>] gfn_to_hva+0x9/0x70 [kvm]
[<ffffffffa088ccd1>] kvm_read_guest_page+0x61/0x70 [kvm]
[<ffffffffa088cd28>] kvm_read_guest+0x48/0x80 [kvm]
[<ffffffffa08931ae>] load_guest_segment_descriptor+0x6e/0xb0 [kvm]
[<ffffffffa0893133>] kvm_queue_exception_e+0x63/0x70 [kvm]
[<ffffffffa08941de>] kvm_task_switch+0x2ee/0x9f0 [kvm]
[<ffffffffa088ed4c>] ioapic_service+0x1ec/0x340 [kvm]
[<ffffffff804b2af7>] __down_read+0x17/0xa6
[<ffffffffa0893566>] kvm_arch_vcpu_ioctl_run+0x266/0x6f0 [kvm]
[<ffffffffa088c502>] kvm_vcpu_ioctl+0x2b2/0x480 [kvm]
[<ffffffff8022ee76>] try_to_wake_up+0xf6/0x1b0
[<ffffffff8022ba4a>] __wake_up_common+0x5a/0x90
[<ffffffff8022bea3>] __wake_up+0x43/0x70
[<ffffffff802556ff>] wake_futex+0x1f/0x30
[<ffffffff80257961>] do_futex+0x881/0xa70
[<ffffffffa08b2ca0>] handle_io+0x0/0x60 [kvm_intel]
[<ffffffff802a0f46>] vfs_ioctl+0x36/0xb0
[<ffffffff802a0f3f>] vfs_ioctl+0x2f/0xb0
[<ffffffff802a124b>] do_vfs_ioctl+0x28b/0x2f0
[<ffffffff802a1351>] sys_ioctl+0xa1/0xb0
[<ffffffff8020bacb>] system_call_fastpath+0x16/0x1b
---[ end trace dc61957677c4cb77 ]---
kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9
------------[ cut here ]------------
WARNING: at arch/x86/kvm/x86.c:185 kvm_queue_exception_e+0x63/0x70
[kvm]()
Modules linked in: tun ext3 jbd mbcache usb_storage cryptomgr cbc
aes_x86_64 aes_generic dm_crypt dm_mod crypto_blkcipher sha256_generic
crypto_algapi coretemp it87 hwmon_vid hwmon snd_seq kvm_intel kvm fuse
nvidia(P) snd_usb_audio snd_hda_intel snd_usb_lib snd_rawmidi
snd_seq_device snd_pcm snd_timer snd_hwdep psmouse thermal ehci_hcd rtc
snd ohci1394 ieee1394 soundcore i2c_core processor snd_page_alloc r8169
button
Pid: 20168, comm: kvm Tainted: P W 2.6.27.3 #1
Call Trace:
[<ffffffff80235c84>] warn_on_slowpath+0x64/0xb0
[<ffffffffa0899c01>] paging64_gva_to_gpa+0x21/0x50 [kvm]
[<ffffffffa088cc09>] gfn_to_hva+0x9/0x70 [kvm]
[<ffffffffa088ccd1>] kvm_read_guest_page+0x61/0x70 [kvm]
[<ffffffffa088cd28>] kvm_read_guest+0x48/0x80 [kvm]
[<ffffffffa08931ae>] load_guest_segment_descriptor+0x6e/0xb0 [kvm]
[<ffffffffa0893133>] kvm_queue_exception_e+0x63/0x70 [kvm]
[<ffffffffa08941de>] kvm_task_switch+0x2ee/0x9f0 [kvm]
[<ffffffffa088ed4c>] ioapic_service+0x1ec/0x340 [kvm]
[<ffffffff804b2af7>] __down_read+0x17/0xa6
[<ffffffffa0893566>] kvm_arch_vcpu_ioctl_run+0x266/0x6f0 [kvm]
[<ffffffffa088c502>] kvm_vcpu_ioctl+0x2b2/0x480 [kvm]
[<ffffffff8022ee76>] try_to_wake_up+0xf6/0x1b0
[<ffffffff8022ba4a>] __wake_up_common+0x5a/0x90
[<ffffffff8022bea3>] __wake_up+0x43/0x70
[<ffffffff802556ff>] wake_futex+0x1f/0x30
[<ffffffff80257961>] do_futex+0x881/0xa70
[<ffffffffa08b2ca0>] handle_io+0x0/0x60 [kvm_intel]
[<ffffffff802a0f46>] vfs_ioctl+0x36/0xb0
[<ffffffff802a0f3f>] vfs_ioctl+0x2f/0xb0
[<ffffffff802a124b>] do_vfs_ioctl+0x28b/0x2f0
[<ffffffff802a1351>] sys_ioctl+0xa1/0xb0
[<ffffffff8020bacb>] system_call_fastpath+0x16/0x1b
---[ end trace dc61957677c4cb77 ]---
kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9
------------[ cut here ]------------
WARNING: at arch/x86/kvm/x86.c:185 kvm_queue_exception_e+0x63/0x70
[kvm]()
Modules linked in: tun ext3 jbd mbcache usb_storage cryptomgr cbc
aes_x86_64 aes_generic dm_crypt dm_mod crypto_blkcipher sha256_generic
crypto_algapi coretemp it87 hwmon_vid hwmon snd_seq kvm_intel kvm fuse
nvidia(P) snd_usb_audio snd_hda_intel snd_usb_lib snd_rawmidi
snd_seq_device snd_pcm snd_timer snd_hwdep psmouse thermal ehci_hcd rtc
snd ohci1394 ieee1394 soundcore i2c_core processor snd_page_alloc r8169
button
Pid: 20168, comm: kvm Tainted: P W 2.6.27.3 #1
Call Trace:
[<ffffffff80235c84>] warn_on_slowpath+0x64/0xb0
[<ffffffffa0899c01>] paging64_gva_to_gpa+0x21/0x50 [kvm]
[<ffffffffa088cc09>] gfn_to_hva+0x9/0x70 [kvm]
[<ffffffffa088ccd1>] kvm_read_guest_page+0x61/0x70 [kvm]
[<ffffffffa088cd28>] kvm_read_guest+0x48/0x80 [kvm]
[<ffffffffa08931ae>] load_guest_segment_descriptor+0x6e/0xb0 [kvm]
[<ffffffffa0893133>] kvm_queue_exception_e+0x63/0x70 [kvm]
[<ffffffffa08941de>] kvm_task_switch+0x2ee/0x9f0 [kvm]
[<ffffffffa088ed4c>] ioapic_service+0x1ec/0x340 [kvm]
[<ffffffff804b2af7>] __down_read+0x17/0xa6
[<ffffffffa0893566>] kvm_arch_vcpu_ioctl_run+0x266/0x6f0 [kvm]
[<ffffffffa088c502>] kvm_vcpu_ioctl+0x2b2/0x480 [kvm]
[<ffffffff8022ee76>] try_to_wake_up+0xf6/0x1b0
[<ffffffff8022ba4a>] __wake_up_common+0x5a/0x90
[<ffffffff8022bea3>] __wake_up+0x43/0x70
[<ffffffff802556ff>] wake_futex+0x1f/0x30
[<ffffffff80257961>] do_futex+0x881/0xa70
[<ffffffffa08b2ca0>] handle_io+0x0/0x60 [kvm_intel]
[<ffffffff802a0f46>] vfs_ioctl+0x36/0xb0
[<ffffffff802a0f3f>] vfs_ioctl+0x2f/0xb0
[<ffffffff802a124b>] do_vfs_ioctl+0x28b/0x2f0
[<ffffffff802a1351>] sys_ioctl+0xa1/0xb0
[<ffffffff8020bacb>] system_call_fastpath+0x16/0x1b
---[ end trace dc61957677c4cb77 ]---
mvh.
Kasper Sandberg
next reply other threads:[~2008-11-22 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 20:49 Kasper Sandberg [this message]
2008-11-23 8:49 ` kvm kernel backtrace 2.6.27.3 using kvm 78 userspace Avi Kivity
2008-11-23 14:23 ` Kasper Sandberg
2008-11-23 14:27 ` Avi Kivity
2008-11-23 16:16 ` Kasper Sandberg
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=1227386974.19624.103.camel@localhost \
--to=lkml@metanurb.dk \
--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.