KVM crash kernel BUG at /build/buildd/linux-2.6.32/arch/x86/kvm/mmu.c:635!

[Alan Bell]

server froze at 1am with no obvious extra load or reason at that time.
stack trace
Dec 12 01:02:01 libertushost2 kernel: [6437696.831762] ------------[ cut here ]------------
Dec 12 01:02:01 libertushost2 kernel: [6437696.843334] kernel BUG at /build/buildd/linux-2.6.32/arch/x86/kvm/mmu.c:635!
Dec 12 01:02:01 libertushost2 kernel: [6437696.866117] invalid opcode: 0000 [#1] SMP
Dec 12 01:02:01 libertushost2 kernel: [6437696.877640] last sysfs file: /sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/irq
Dec 12 01:02:01 libertushost2 kernel: [6437696.899839] CPU 7
Dec 12 01:02:01 libertushost2 kernel: [6437696.910604] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm bridge stp fbcon tileblit font bitblit softcursor snd_hda_codec_atihdmi vga16fb vgastate snd_hda_intel snd_hda_codec radeon f71882fg ttm snd_hwdep snd_pcm drm_kms_helper snd_timer drm snd lp soundcore snd_page_alloc i2c_algo_bit parport multipath linear aacraid 3w_9xxx 3w_xxxx raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 ahci r8169 mii sata_nv sata_sil sata_via
Dec 12 01:02:01 libertushost2 kernel: [6437697.008100] Pid: 3958, comm: kvm Not tainted 2.6.32-41-server #90-Ubuntu MS-7522
Dec 12 01:02:01 libertushost2 kernel: [6437697.027648] RIP: 0010:[<ffffffffa0301370>] [<ffffffffa0301370>] rmap_remove+0x1b0/0x1c0 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.047521] RSP: 0018:ffff8805f8c15a68 EFLAGS: 00010292
Dec 12 01:02:01 libertushost2 kernel: [6437697.057045] RAX: 000000000000003e RBX: ffff880522331758 RCX: 0000000000000000
Dec 12 01:02:01 libertushost2 kernel: [6437697.074618] RDX: 0000000000000000 RSI: 0000000000000082 RDI: 0000000000000246
Dec 12 01:02:01 libertushost2 kernel: [6437697.093284] RBP: ffff8805f8c15a88 R08: 00000000ffffffff R09: 0000000000000000
Dec 12 01:02:01 libertushost2 kernel: [6437697.111726] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8805f8c10000
Dec 12 01:02:01 libertushost2 kernel: [6437697.130112] R13: 0000000000000000 R14: ffff88043560d420 R15: 00000000000000eb
Dec 12 01:02:01 libertushost2 kernel: [6437697.148973] FS: 00007f6460cae700(0000) GS:ffff880016ee0000(0000) knlGS:0000000000000000
Dec 12 01:02:01 libertushost2 kernel: [6437697.167953] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Dec 12 01:02:01 libertushost2 kernel: [6437697.177741] CR2: 00007f7f2214c088 CR3: 00000005fe51e000 CR4: 00000000000026e0
Dec 12 01:02:01 libertushost2 kernel: [6437697.197519] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 12 01:02:01 libertushost2 kernel: [6437697.217445] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 12 01:02:01 libertushost2 kernel: [6437697.237674] Process kvm (pid: 3958, threadinfo ffff8805f8c14000, task ffff8806124d4500)
Dec 12 01:02:01 libertushost2 kernel: [6437697.258272] Stack:
Dec 12 01:02:01 libertushost2 kernel: [6437697.268478] ffff88043560d420 ffff8805f8c10000 ffff880522331758 0000000000000000
Dec 12 01:02:01 libertushost2 kernel: [6437697.278991] <0> ffff8805f8c15ac8 ffffffffa0301c44 8000000000000163 ffff8805f8c10000
Dec 12 01:02:01 libertushost2 kernel: [6437697.299855] <0> ffff880163a7a0b0 ffff8805f8c13878 0000000000000001 00000000000e0000
Dec 12 01:02:01 libertushost2 kernel: [6437697.330826] Call Trace:
Dec 12 01:02:01 libertushost2 kernel: [6437697.341064] [<ffffffffa0301c44>] kvm_mmu_zap_page+0x84/0x380 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.351264] [<ffffffffa0302188>] kvm_mmu_zap_all+0x38/0x70 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.361298] [<ffffffffa02f4856>] kvm_arch_flush_shadow+0x16/0x30 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.371132] [<ffffffffa02eb421>] __kvm_set_memory_region+0x6e1/0x770 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.380915] [<ffffffffa02fd444>] ? kvm_emulate_pio+0x174/0x1c0 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.390602] [<ffffffffa02eb4f3>] kvm_set_memory_region+0x43/0x70 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.400167] [<ffffffffa02eb53d>] kvm_vm_ioctl_set_memory_region+0x1d/0x30 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.418680] [<ffffffffa02ec5b2>] kvm_vm_ioctl+0x282/0x6d0 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.427772] [<ffffffffa0349a6a>] ? vmx_handle_exit+0xca/0x250 [kvm_intel]
Dec 12 01:02:01 libertushost2 kernel: [6437697.436826] [<ffffffffa03451da>] ? __vmx_load_host_state+0x1ba/0x220 [kvm_intel]
Dec 12 01:02:01 libertushost2 kernel: [6437697.454628] [<ffffffffa034524e>] ? vmx_vcpu_put+0xe/0x10 [kvm_intel]
Dec 12 01:02:01 libertushost2 kernel: [6437697.463532] [<ffffffffa02efbbb>] ? kvm_arch_vcpu_put+0x1b/0x50 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.472292] [<ffffffffa02ebd88>] ? vcpu_put+0x28/0x30 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.480874] [<ffffffffa02fd544>] ? kvm_arch_vcpu_ioctl_run+0xb4/0x1d0 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.497542] [<ffffffff8105dd2b>] ? try_to_wake_up+0x2fb/0x480
Dec 12 01:02:01 libertushost2 kernel: [6437697.505818] [<ffffffff81560cbe>] ? _spin_lock+0xe/0x20
Dec 12 01:02:01 libertushost2 kernel: [6437697.513944] [<ffffffff81097cc2>] ? futex_wake+0x112/0x130
Dec 12 01:02:01 libertushost2 kernel: [6437697.521905] [<ffffffff81157442>] vfs_ioctl+0x22/0xa0
Dec 12 01:02:01 libertushost2 kernel: [6437697.529663] [<ffffffff811575e1>] do_vfs_ioctl+0x81/0x410
Dec 12 01:02:01 libertushost2 kernel: [6437697.537262] [<ffffffff8109a2eb>] ? sys_futex+0x7b/0x170
Dec 12 01:02:01 libertushost2 kernel: [6437697.544789] [<ffffffff811579f1>] sys_ioctl+0x81/0xa0
Dec 12 01:02:01 libertushost2 kernel: [6437697.552340] [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Dec 12 01:02:01 libertushost2 kernel: [6437697.559785] Code: 8b 13 48 89 de 48 c7 c7 f0 70 31 a0 31 c0 e8 31 cc 25 e1 0f 0b eb fe 48 8b 13 48 89 de 48 c7 c7 d0 70 31 a0 31 c0 e8 19 cc 25 e1 <0f> 0b eb fe 48 8b 17 48 89 10 eb a8 0f 1f 40 00 55 48 89 e5 41
Dec 12 01:02:01 libertushost2 kernel: [6437697.584534] RIP [<ffffffffa0301370>] rmap_remove+0x1b0/0x1c0 [kvm]
Dec 12 01:02:01 libertushost2 kernel: [6437697.592030] RSP <ffff8805f8c15a68>
Dec 12 01:02:01 libertushost2 kernel: [6437697.605688] ---[ end trace 2f6d14a31947ff45 ]---

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-43-server 2.6.32-43.97
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-43.97-server 2.6.32.59+drm33.24
Uname: Linux 2.6.32-43-server x86_64
Architecture: amd64
Date: Wed Dec 12 12:41:47 2012
Frequency: This has only happened once.
InstallationMedia:

ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.04
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=27b2f2d3-0ec2-4f22-9f6d-c857b6830ab6
InstallationMedia:

IwConfig: Error: [Errno 2] No such file or directory
MachineType: MSI MS-7522
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-43-server root=UUID=f036abbe-40b4-45fc-b4b7-6e7eb5994fd7 ro nomodeset
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-43.97-server 2.6.32.59+drm33.24
Regression: No
RelatedPackageVersions: linux-firmware 1.34.14
Reproducible: No
RfKill: Error: [Errno 2] No such file or directory
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-43-server x86_64
UserGroups:

dmi.bios.date: 11/02/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V8.14
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MSI X58 Pro-E (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.14:bd11/02/2010:svnMSI:pnMS-7522:pvr3.0:rvnMSI:rnMSIX58Pro-E(MS-7522):rvr3.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr3.0:
dmi.product.name: MS-7522
dmi.product.version: 3.0
dmi.sys.vendor: MSI

[Colin Ian King (colin-king)]

Initial observation, this looks similar: http://lkml.indiana.edu/hypermail/linux/net/1102.0/00008.html

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1089341

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Alan Bell (alanbell)]

apport information

[Colin Ian King (colin-king)]

Alan, I can't see what is triggering this failure. If you see it again can you report back. Thanks

[Colin Ian King (colin-king)]

This bug has not been updated since December 2012. Marking it as won't fix. If the issue occurs again, please re-open the bug.