WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: xen_pgd_pin BUG

To: Kimball Murray <kimball.murray@xxxxxxxxx>
Subject: [Xen-devel] Re: xen_pgd_pin BUG
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 08:21:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 02 Apr 2008 00:22:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bbe04eb10804011239h3fd2204cyd1e00a7eb4ee4204@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciUki9QbcwmfACFEd24ZAAWy6hiGQ==
Thread-topic: xen_pgd_pin BUG
User-agent: Microsoft-Entourage/11.4.0.080122
What dom0 kernel are you running? What version of Xen?

 -- Keir

On 1/4/08 20:39, "Kimball Murray" <kimball.murray@xxxxxxxxx> wrote:

> Greetings.  I'm running a system with a single, HVM guest.  When I
> delete the guest, I trigger a BUG_ON statement in xen_pgd_pin
> (arch/i386/mm/hypervisor.c), which crashes dom0.  I did see some
> chatter about this same bug in various contexts a while ago, but
> didn't notice if there had been a resolution.  If it has been
> resolved, could someone point me in the right direction?  Thanks!
> 
> (XEN) mm.c:1769:d0 Bad type (saw 00000000e8000001 != exp 0000000020000000) for
> m
> fn 20cfa4 (pfn 1bda4)
> (XEN) mm.c:657:d0 Attempt to create linear p.t. with write perms
> (XEN) mm.c:1082:d0 Failure in alloc_l2_table: entry 2
> (XEN) mm.c:1790:d0 Error while validating mfn 1fbf62 (pfn 2cd62) for type
> 000000
> 0040000000: caf=80000003 taf=0000000040000001
> (XEN) mm.c:1156:d0 Failure in alloc_l3_table: entry 0
> (XEN) mm.c:1790:d0 Error while validating mfn 2007e1 (pfn 285e1) for type
> 000000
> 0060000000: caf=80000003 taf=0000000060000001
> (XEN) mm.c:2059:d0 Error while pinning mfn 2007e1
> ------------[ cut here ]------------
> kernel BUG at arch/i386/mm/hypervisor.c:186!
> invalid opcode: 0000 [#1]
> SMP
> last sysfs file: /class/net/biz0/bridge/forward_delay
> Modules linked in: tun mptctl mptbase usbhid dell_rbu firmware_class drbd cn
> ipm
> i_devintf ipmi_si ipmi_msghandler bridge ipv6 binfmt_misc dm_mirror
> dm_multipath
>  dm_mod video thermal sbs processor i2c_ec i2c_core fan container button
> battery
>  asus_acpi ac parport_pc lp parport nvram sr_mod cdrom evdev sg piix pcspkr
> ata_
> piix shpchp libata bnx2 pci_hotplug zlib_inflate serial_core serio_raw rtc
> ide_d
> isk megaraid_sas sd_mod scsi_mod raid1 ehci_hcd ohci_hcd uhci_hcd usbcore
> CPU:    0
> EIP:    0061:[<c011af1e>]    Not tainted VLI
> EFLAGS: 00210282  (2.6.18-8.1.8.el5.xs4.0.1.125.163xen #1)
> EIP is at xen_pgd_pin+0x6e/0x80
> eax: ffffffea  ebx: ec353ebc  ecx: 00000001  edx: 00000000
> esi: 00007ff0  edi: 00000000  ebp: ec353ed0  esp: ec353ebc
> ds: 007b  es: 007b  ss: 0069
> Process spine (pid: 8727, ti=ec352000 task=dcf9f7f0 task.ti=ec352000)
> Stack: 00000002 002007e1 00000000 0050bc20 d9c026fc ec353edc c0115852 df8ae200
>       ec353ee8 c011587f 01200011 ec353ef0 c0116519 ec353f64 c0122c69 d9c02b90
>       dcd9dddc dcd9dddc c06a7778 df8ae238 efb8eeec ec353fbc bfc97874 00000000
> Call Trace:
>  [<c010640a>] show_trace_log_lvl+0x1a/0x30
>  [<c01064d1>] show_stack_log_lvl+0xb1/0xe0
>  [<c01066aa>] show_registers+0x1aa/0x230
>  [<c010687a>] die+0x14a/0x310
>  [<c0106abf>] do_trap+0x7f/0xb0
>  [<c0107357>] do_invalid_op+0x97/0xb0
>  [<c0105cdb>] error_code+0x2b/0x30
>  [<c0115852>] __pgd_pin+0x32/0x40
>  [<c011587f>] mm_pin+0x1f/0x30
>  [<c0116519>] _arch_dup_mmap+0x29/0x30
>  [<c0122c69>] copy_process+0x1139/0x12d0
>  [<c0122e50>] do_fork+0x50/0x150
>  [<c010322f>] sys_clone+0x2f/0x40
>  [<c0105b37>] syscall_call+0x7/0xb
>  =======================
> Code: 31 d2 be f0 7f 00 00 e8 41 64 fe ff 85 c0 78 1b 8b 5d f8 8b 75 fc 89 ec
> 5d
>  c3 8d 76 00 39 c2 72 c6 0f 0b 22 00 24 74 32 c0 eb bc <0f> 0b ba 00 3a 97 32
> c0
>  eb db 90 8d b4 26 00 00 00 00 55 89 c2



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Re: xen_pgd_pin BUG, Keir Fraser <=