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] xen assert in latest 3.3.2-rc bits

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen assert in latest 3.3.2-rc bits
From: Mark Johnson <johnson.nh@xxxxxxxxx>
Date: Tue, 10 Mar 2009 17:39:49 -0400
Delivery-date: Tue, 10 Mar 2009 14:40:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=500cMMpQNctrFxL72dSofZ/5rhIFAicIUV6/K6a8mSQ=; b=LnY+kPcP2Qo7AStPW2UZDwxr0xqyD0+QsxUXdQElLUz6v2uxVQN7uyy+EIvGa3ertK BN7z15o2+8Pk0jB+Ev8+NRVz+ENJ5/8RJN+Ak4LDkY19lViyTsKCI/D+nck0g9kahj40 VrNJCJawCEduz3TNrRCtPaLUwO/MZxxb++S3I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=IJ2OHUVDfw9C93wLcPsAlnPiF4799lxoJjZ6yt/FnplsNSaWVPtVBfe/CdASyJ0m11 vkONc5/nyrC8nulwY8lz6mP3NsqEJcxVo2KG0iKlo/8b/tVD0Jf0mFa8H1eAGd6cfaNt h9jbDVKSDGzzOHqfUQMw2Ke5IQZBHPILMS56Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I just got the following assertion when shutting down a windows 7 guest on
the latest 3.3-testing bits.. Has anyone else seen this?


MRJ


(xVM) Assertion 'd->dirty_vram->sl1ma[i] == sl1ma' failed at multi.c:1376
(xVM) ----[ Xen-3.3.2-rc1-pre-xvm-debug  x86_64  debug=y  Not tainted ]----
(xVM) CPU:    1
(xVM) RIP:    e008:[<ffff828c801b8641>]
sh_destroy_l1_shadow__guest_2+0x247/0x56c
(xVM) RFLAGS: 0000000000010287   CONTEXT: hypervisor
(xVM) rax: ffff8300ceeda100   rbx: 000000000012ffbe   rcx: 000000000000001d
(xVM) rdx: 0000000000000001   rsi: ffff8300ceecc100   rdi: 000000003a5fd025
(xVM) rbp: ffff8300cee0fbf8   rsp: ffff8300cee0fba8   r8:  ffff8300ceece100
(xVM) r9:  000000012ffbe0e8   r10: ffff83012ffbe0e8   r11: 0000000000000000
(xVM) r12: ffff83012ffbe0e8   r13: 000000000000001d   r14: ffff8300ceece100
(xVM) r15: ffff83012ffbe000   cr0: 000000008005003b   cr4: 00000000000026f0
(xVM) cr3: 00000000cad23000   cr2: fffffe00521aa128
(xVM) ds: 004b   es: 004b   fs: 0000   gs: 0000   ss: e010   cs: e008
(xVM) Xen stack trace from rsp=ffff8300cee0fba8:
(xVM)    555555555555beef 00000000000000be ffff8300ceece100 000000000012ffbe
(xVM)    ffff8300ceede100 ffff828402f7f5b0 0000000000000000 000000000012ffbe
(xVM)    0000000000000180 000000000012ffd3 ffff8300cee0fc08 ffff828c801b06e2
(xVM)    ffff8300cee0fc68 ffff828c801b83a7 ffff8300ceede100 ffff83012ffd3000
(xVM)    0000000300000000 000000000012ffd0 ffff8300ceede100 ffff828402f7f880
(xVM)    0000000000000000 000000000012ffd0 ffff8300ceece100 0000000000000002
(xVM)    ffff8300cee0fc78 ffff828c801b06ec ffff8300cee0fce8 ffff828c801ae3dd
(xVM)    000000008284f5d1 0000000000000000 ffff8300ceede100 ffff8300ceede100
(xVM)    ffff828401323708 ffff8300ceede100 00000001cee0fce8 ffff8300ceece100
(xVM)    0000000000000000 ffff8300ceedfb20 0000000000000002 0000000000000004
(xVM)    ffff8300cee0fd48 ffff828c801afa13 0000000800000000 ffff8300cee0ff28
(xVM)    ffff8300ceece120 0000000000000020 0000000000000000 ffff8300ceecf0b0
(xVM)    0000000000000000 ffff8300ceedfb20 ffff828c802b90c0 ffff8300ceece100
(xVM)    ffff8300cee0fd88 ffff828c801b4925 0000000000000000 ffff8300ceece100
(xVM)    ffff8300ceece100 00007ffffd0ef360 fffffffffffffffd ffffff00047c7e24
(xVM)    ffff8300cee0fda8 ffff828c801a961a ffff8300cee0fdc8 ffff8300ceece100
(xVM)    ffff8300cee0fdc8 ffff828c80141f17 ffff8300ceece100 0000000000000000
(xVM)    ffff8300cee0fdf8 ffff828c801056bd ffff828401fb0d90 ffff828c80240340
(xVM)    ffff8300cee0fe48 ffffff00047c7b60 ffff8300cee0ff08 ffff828c80104791
(xVM)    ffff828401fdd368 ffff828c80240340 0000000000000002 0000000080000000
(xVM) Xen call trace:
(xVM)    [<ffff828c801b8641>] sh_destroy_l1_shadow__guest_2+0x247/0x56c
(xVM)    [<ffff828c801b06e2>] sh_destroy_shadow+0xcd/0x16f
(xVM)    [<ffff828c801b83a7>] sh_destroy_l2_shadow__guest_2+0x2be/0x311
(xVM)    [<ffff828c801b06ec>] sh_destroy_shadow+0xd7/0x16f
(xVM)    [<ffff828c801ae3dd>] _shadow_prealloc+0x3cb/0x578
(xVM)    [<ffff828c801afa13>] sh_set_allocation+0x1ec/0x356
(xVM)    [<ffff828c801b4925>] shadow_teardown+0x2bf/0x461
(xVM)    [<ffff828c801a961a>] paging_teardown+0x30/0x3f
(xVM)    [<ffff828c80141f17>] domain_relinquish_resources+0x51/0x16d
(xVM)    [<ffff828c801056bd>] domain_kill+0x87/0x182
(xVM)    [<ffff828c80104791>] do_domctl+0x58c/0xcdb
(xVM)    [<ffff828c801d81bf>] syscall_enter+0xef/0x149
(xVM)
Xen panic[dom=0xffff8300ceefa100/vcpu=0xffff8300cfde4100]: Assertion
'd->dirty_vram->sl1ma[i] == sl1ma' failed at multi.c:1376

        rdi: ffff828c801f9b68 rsi: ffff8300cee0f9a8 rdx: ffff828c80159deb
        rcx:              560  r8: ffff8300cee0ff08  r9: ffff8300cee0ff18
        rax: ffff8300cee0f9c8 rbx: ffff828c801f9b68 rbp: ffff8300cee0fa88
        r10: ffff828c8029fdc0 r11: ffff8300cee0fa08 r12:              282
        r13: ffff8300cee0f928 r14: ffff828c8029fdc1 r15:       3000000008
        fsb:     7ffffe934a00 gsb: fffffffffbc619b0  ds:               4b
         es:               4b  fs:                0  gs:                0
         cs:             e008 rfl:              282 rsp: ffff8300cee0f9a0
        rip: ffff828c80159e40:  ss:             e010
        cr0: 8005003b  cr2: fffffe00521aa128  cr3: cad23000  cr4:     26f0

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