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] BUG at xen/include/asm/shadow2.h: 409

To: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] BUG at xen/include/asm/shadow2.h: 409
From: Gerd Hoffmann <kraxel@xxxxxxx>
Date: Mon, 21 Aug 2006 14:08:57 +0200
Delivery-date: Mon, 21 Aug 2006 05:09:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird 1.5.0.5 (X11/20060725)
  Hi,

$subject says all, full log attached.

This is while playing with kexec where domU switches from one
self-consistent page table tree to a new self-consistent page table
tree, but the new page table tree does NOT map the old page table pages
read-only (and visa-versa).  In that (rare) case the verification of the
new page table tree happens with the idle page tables active.

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@xxxxxxx>
http://www.suse.de/~kraxel/julika-dora.jpeg
(XEN) DOM1: (file=mm.c, line=1697) Bad type (saw e8000001 != exp 40000000) for 
mfn 17fbe (pfn 667e)
(XEN) DOM1: (file=mm.c, line=1781) New baseptr 17fbe: slow path via idle 
pagetables
(XEN) BUG at 
/home/kraxel/xen/build-32-unstable-11211/xen/include/asm/shadow2.h:409
(XEN) 0f 0b eb fe 90
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    e008:[<ff116fa4>] __bug+0x24/0x30
(XEN) EFLAGS: 00010282   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ff19d080   ecx: 0000000a   edx: 00000000
(XEN) esi: ff1dbfb4   edi: 00017fbe   ebp: ffbee080   esp: ff1dbf00
(XEN) cr0: 8005003b   cr3: 17235000
(XEN) ds: e010   es: e010   fs: e021   gs: e021   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff1dbf00:
(XEN)    ff16959f ff1682d0 00000199 ff124f05 ff1682d0 00000199 000006f5 00017fbe
(XEN)    ff1dbfb4 ff1dbfb4 00017235 ff19d080 00000000 ff1dbfb4 ff1dbfb4 ff12c945
(XEN)    00017fbe ff1dbfb4 00000000 00017fbe 0001dedf 00000001 ff19d080 ff1dbfb4
(XEN)    fee8e000 00017fbe ff19d080 ff19dc80 ff19d080 0019d080 c010ca89 00000000
(XEN)    c7ba5c1c 17fbec7c 00000000 17f9e0d8 00000000 00000000 00000001 ff19d080
(XEN)    c010cc37 c667d07b c7ba5e88 ff15396e ff1dbfb4 00000020 00000000 0667d000
(XEN)    c010cc37 c667d07b c7ba5e88 17fbe000 000d0000 c010ca86 0000e019 00010207
(XEN)    c7ba5e38 0000e021 0000e021 0000e021 0000e021 0000e021 00000001 ff19d080
(XEN) Xen call trace:
(XEN)    [<ff116fa4>] __bug+0x24/0x30
(XEN)    [<ff124f05>] new_guest_cr3+0x175/0x460
(XEN)    [<ff12c945>] do_general_protection+0xf85/0x1000
(XEN)    [<ff15396e>] handle_exception+0x5e/0x8e
(XEN)    
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) CPU1 FATAL TRAP: vector = 6 (invalid opcode)
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>