Re: oops in kvm:gfn_to_rmap

[Marcelo Tosatti <mtosatti@redhat.com>]

On Mon, Mar 02, 2009 at 08:48:16AM +0000, Adrian Bridgett wrote:
> We've had two machines crash (at a weekend of course! \o/ for IPMI
> remote reboot!) - both times the machines were pingable but ssh failed
> (no ssh banner via telnet). This time there was an oops.
> 
> host is debian lenny:
> linux-image-2.6.26-1-amd64
> kvm: 83+dfsg-1
> 
> box has several SMP guests on it and had been stable until quite
> recently (I think it's a pure load issue).  Quad core Xeon E5420, 16GB
> RAM.  Box oops is from has these guests:
> - Windows SBS 2008 (4GB - no virtio yet)
> - Centos 5.2 (4GB, no virtio (will change that!))
> - Vista 32bit (1GB virtio)
> - Windows 2003 web edition (1GB virtio)
> 
> Googling shows a patch from last year which I presume is in kvm-83:
> http://www.mail-archive.com/kvm@vger.kernel.org/msg01312.html
> 
> Oops follows:

Adrian,

Please paste a few lines above

PGD 27a874067 PUD 4ba84d067 PMD 0 CPU 2

Thanks

> 
> PGD 27a874067 PUD 4ba84d067 PMD 0 
> CPU 2 
> Modules linked in: ipmi_watchdog ipmi_devintf ipmi_si ipmi_msghandler tun kvm_intel kvm ipv6 bridge loop snd_pcm snd_timer snd soundcore snd_page_alloc iTCO_wdt pcspkr serio_raw psmouse rng_core usbhid hid i5000_edac ff_memless edac_core button shpchp pci_hotplug evdev dcdbas ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sr_mod cdrom ide_pci_generic ide_core ata_generic sd_mod ata_piix libata dock ehci_hcd uhci_hcd mptsas mptscsih mptbase scsi_transport_sas scsi_mod bnx2 firmware_class thermal processor fan thermal_sys
> Pid: 1999, comm: kvm Not tainted 2.6.26-1-amd64 #1
> RIP: 0010:[<ffffffffa02935c4>]  [<ffffffffa02935c4>] :kvm:gfn_to_rmap+0x17/0x49
> RSP: 0018:ffff81000a59ba38  EFLAGS: 00010246
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 00000000000fee01 RSI: fffffffffffff001 RDI: ffff810449894000
> RBP: fffffffffffff001 R08: 000000000000000a R09: 000000000000000a
> R10: 0000000000411ef1 R11: 000000000000000b R12: ffff810174746ea0
> R13: ffff810449894000 R14: ffff8101c90bc000 R15: ffffffffa02a9e00
> FS:  0000000040bfa950(0000) GS:ffff8104bccfff40(0000) knlGS:0000000000000000
> CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
> CR2: 0000000000000000 CR3: 000000048dff5000 CR4: 00000000000026e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process kvm (pid: 1999, threadinfo ffff81000a59a000, task ffff8104bcec6280)
> Stack:  00000000002486dd 00000000002486dd ffff8101c90bc038 ffffffffa02936a5
>  000000000000000b ffff8101c90bc038 ffff810174746ea0 ffff810449894000
>  0000000000000038 ffffffffa029383a 0000000000000010 ffff81000a5614d8
> Call Trace:
>  [<ffffffffa02936a5>] ? :kvm:rmap_remove+0xaf/0x198
>  [<ffffffffa029383a>] ? :kvm:kvm_mmu_zap_page+0x8a/0x270
>  [<ffffffffa0294f1a>] ? :kvm:kvm_mmu_pte_write+0x2aa/0x721
>  [<ffffffffa0295c86>] ? :kvm:paging64_gva_to_gpa+0x21/0x44
>  [<ffffffffa028c79b>] ? :kvm:mark_page_dirty+0x1c/0x3f
>  [<ffffffffa028f87a>] ? :kvm:emulator_write_phys+0x36/0x46
>  [<ffffffffa0290c93>] ? :kvm:emulator_write_emulated_onepage+0x68/0xe6
>  [<ffffffffa029ab36>] ? :kvm:x86_emulate_insn+0x378f/0x4245
>  [<ffffffffa02972b2>] ? :kvm:x86_decode_insn+0x9e4/0xad9
>  [<ffffffffa028f711>] ? :kvm:emulate_instruction+0x1a0/0x2d3
>  [<ffffffffa0294c35>] ? :kvm:kvm_mmu_page_fault+0x46/0x81