public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org>
To: Pedro Alves <pedro-x9W5mcYdYeS4rn6H26CGUg@public.gmane.org>
Cc: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: kvm-48: kernel BUG at mmu.c:307! - invalid opcode: 0000 [#1]
Date: Fri, 26 Oct 2007 16:57:51 +0200	[thread overview]
Message-ID: <20071026145751.GA4838@hall.aurel32.net> (raw)
In-Reply-To: <20071026140906.GA7545-8+64PGVKDrE@public.gmane.org>

On Fri, Oct 26, 2007 at 03:09:06PM +0100, Pedro Alves wrote:
> 
> 
> Hello.
> 
> I've been using kvm for a while, and it's been working great so far. Today
> I got a kernel error pasted below.

Strangely I got the same problem one or two hours ago.

Here are some info about the host:
- Distribution: Debian
- Architecture: x86_64
- Kernel: 2.6.22-2
- CPU: Intel Core 2 Q6600
- KVM 48

The system is running 10 KVM guests and the operating systems are BSD, Linux, Hurd, GNU/kFreeBSD.

Only one of the two GNU/kFreeBSD amd64 guests crashed, the others are
still running fine. It was under heavy load (building a glibc).

And the dmesg log:


------------[ cut here ]------------
kernel BUG at /usr/local/src/kvm-48/kernel/mmu.c:307!
invalid opcode: 0000 [1] SMP 
CPU 3 
Modules linked in: usb_storage kvm_intel kvm cpufreq_userspace nfs nfsd exportfs lockd nfs_acl sunrpc ppdev lp button ac battery xt_mark xt_MARK ipt_REDIRECT ipt_REJECT ipt_recent xt_state ipt_TOS xt_tcpudp ipt_LOG xt_limit iptable_mangle iptable_nat nf_conntrack_ipv4 iptable_filter ip_tables x_tables nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntrack_rtsp nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp nf_nat_irc nf_nat nf_conntrack_irc nf_conntrack nfnetlink aoe sit tunnel4 wlan_wep bridge quota_v2 dm_snapshot dm_mirror dm_mod cpufreq_stats cpufreq_ondemand acpi_cpufreq freq_table tun loop it87 hwmon_vid i2c_isa coretemp 8021q ipv6 snd_hda_intel ftdi_sio wlan_scan_ap snd_pcm snd_timer snd ath_rate_sample usbserial evdev intel_agp soundcore snd_page_alloc i2c_i801 ath_pci wl
 an usblp i2c_core ath_hal(P) parport_pc parport pcspkr ext3 jbd mbcache raid456 xor raid1 raid0 md_mod ide_generic ide_cd cdrom ata_generic sd_mod usbhid hid jmicron r8169 firewire_ohci fire
 wire_core crc_itu_t ahci generic ide_core e1000 ehci_hcd libata scsi_mod uhci_hcd thermal processor fan
Pid: 11409, comm: qemu-system-x86 Tainted: P       2.6.22-2-amd64 #1
RIP: 0010:[<ffffffff8839a3dd>]  [<ffffffff8839a3dd>] :kvm:mmu_memory_cache_alloc+0xd/0x29
RSP: 0018:ffff8102206a39c8  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffc20013238810 RCX: 0000000000000028
RDX: ffff810133d84088 RSI: 0000000000000028 RDI: ffff8101c5b04758
RBP: ffff8101c5b04440 R08: 0000000000000000 R09: 0000000000000004
R10: 00000000071c2067 R11: ffffffff885a137c R12: ffff8101009c6010
R13: 0000000000000002 R14: ffff8101c5b04440 R15: ffff8101009c6010
FS:  00002b2e3cc37550(0000) GS:ffff810227b29b40(0000) knlGS:0000000000000000
CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000005b19a4 CR3: 000000014f225000 CR4: 00000000000026e0
Process qemu-system-x86 (pid: 11409, threadinfo ffff8102206a2000, task ffff810226c370a0)
Stack:  00000000000071c2 ffffffff8839a48c 000000018c586047 000000018c586000
 0000000000000045 ffffffff8839ae92 0000000000000001 00000000000071c2
 0000000000000000 0000000000000000 00000000071c2000 00000000071c2000
Call Trace:
 [<ffffffff8839a48c>] :kvm:rmap_add+0x85/0xe7
 [<ffffffff8839ae92>] :kvm:paging64_set_pte_common+0x1c5/0x22e
 [<ffffffff8839af45>] :kvm:paging64_set_pte+0x4a/0x4f
 [<ffffffff8839b202>] :kvm:kvm_mmu_pte_write+0x2b8/0x328
 [<ffffffff88396581>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8839f697>] :kvm:x86_emulate_insn+0x2ba1/0x4146
 [<ffffffff8839c85d>] :kvm:x86_decode_insn+0x78c/0xa25
 [<ffffffff885a1377>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88396a57>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff885a3a57>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff88397492>] :kvm:kvm_vcpu_ioctl+0x357/0xf57
 [<ffffffff80229db3>] task_rq_lock+0x3d/0x6f
 [<ffffffff80229976>] __activate_task+0x26/0x38
 [<ffffffff8038b360>] memcpy_toiovec+0x36/0x66
 [<ffffffff8038b7aa>] skb_copy_datagram_iovec+0x49/0x1ed
 [<ffffffff80243de3>] remove_wait_queue+0x12/0x45
 [<ffffffff883b998f>] :tun:tun_chr_aio_read+0x2a8/0x2ba
 [<ffffffff8028fe5c>] core_sys_select+0x234/0x265
 [<ffffffff8023aec4>] __dequeue_signal+0x19/0x15a
 [<ffffffff8023c4bc>] dequeue_signal+0xa5/0x126
 [<ffffffff8024722b>] getnstimeofday+0x32/0x8b
 [<ffffffff8028eb9f>] do_ioctl+0x2b/0xb6
 [<ffffffff8028ee77>] vfs_ioctl+0x24d/0x266
 [<ffffffff8028eee9>] sys_ioctl+0x59/0x7c
 [<ffffffff80209d8e>] system_call+0x7e/0x83


Code: 0f 0b eb fe ff c8 89 07 48 98 48 8b 54 c7 08 31 c0 fc 48 89 
RIP  [<ffffffff8839a3dd>] :kvm:mmu_memory_cache_alloc+0xd/0x29
 RSP <ffff8102206a39c8>


-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org         | aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org
   `-    people.debian.org/~aurel32 | www.aurel32.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

      parent reply	other threads:[~2007-10-26 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 14:09 kvm-48: kernel BUG at mmu.c:307! - invalid opcode: 0000 [#1] Pedro Alves
     [not found] ` <20071026140906.GA7545-8+64PGVKDrE@public.gmane.org>
2007-10-26 14:57   ` Aurelien Jarno [this message]

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=20071026145751.GA4838@hall.aurel32.net \
    --to=aurelien-rxxeib44qovr7s880joybq@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pedro-x9W5mcYdYeS4rn6H26CGUg@public.gmane.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