|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] RE: hypervisor crash in map_vtd_domain_page
To: |
"Kay, Allen M" <allen.m.kay@xxxxxxxxx> |
Subject: |
[Xen-devel] RE: hypervisor crash in map_vtd_domain_page |
From: |
Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> |
Date: |
Fri, 14 Jan 2011 08:57:05 +0000 |
Cc: |
"Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>, "You, Yongkang" <yongkang.you@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx> |
Delivery-date: |
Fri, 14 Jan 2011 00:58:27 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<987664A83D2D224EAE907B061CE93D5301941079FE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
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> |
Organization: |
Citrix Systems, Inc. |
References: |
<1294913510.8240.30.camel@xxxxxxxxxxxxxxxxxxxxxx> <987664A83D2D224EAE907B061CE93D5301941079FE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Thu, 2011-01-13 at 18:38 +0000, Kay, Allen M wrote:
> Ian/Keir,
>
> The attached patch should fix the crash issue. Somehow the check for
> !iommu_hap_pt_share in function iommu_set_pgd() got dropped in changeset
> 22692.
>
> Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx>
Works for me. Thanks.
Tested-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
>
> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
> Sent: Thursday, January 13, 2011 2:12 AM
> To: Kay, Allen M
> Cc: Keir Fraser; xen-devel
> Subject: hypervisor crash in map_vtd_domain_page
>
> Hi Allen,
>
> When I try and start an HVM guest with a passed through PCI device I
> immediately get the hypervisor crash below.
>
> Domain 0 is xen/stable-2.6.32.x if that matters. The two devices are USB
> controllers.
>
> Based on the hg log of xen/drivers/passthrough I reverted
> 22697:1ae74f060a39+22696:f5b3fc5a5220+22695:55450858f414 and reapplied
> the build fix bit of 22695:55450858f414 and that still failed.
>
> I then reverted 22692:66e806289464 and now my guest boots fine.
>
> Ian.
>
> (XEN) Assertion 'ma < ((((((262UL) >> 8) * 0xffff000000000000UL) | (262UL <<
> 39))) + ((1UL << 39)*10)) - (((((262UL) >> 8) * 0xffff000000000000UL) |
> (262UL << 39)))' failed at
> /local/scratch/ianc/devel/xen-unstable.hg/xen/incl:98
> (XEN) ----[ Xen-4.1-unstable x86_64 debug=y Not tainted ]----
> (XEN) CPU: 5
> (XEN) RIP: e008:[<ffff82c48014725d>] map_vtd_domain_page+0x1d/0x58
> (XEN) RFLAGS: 0000000000010212 CONTEXT: hypervisor
> (XEN) rax: 000004ffffffffff rbx: ffff8306221da000 rcx: 0000000000000027
> (XEN) rdx: 1c000006221d9000 rsi: 0000000000000000 rdi: 1c000006221d9007
> (XEN) rbp: ffff830631167b68 rsp: ffff830631167b68 r8: ffff82c48014261a
> (XEN) r9: 0000000000000001 r10: 0000000000000000 r11: 0000000000000000
> (XEN) r12: 0000000000000012 r13: 0000000000000004 r14: 0000000000000027
> (XEN) r15: ffff8306221da000 cr0: 000000008005003b cr4: 00000000000026f0
> (XEN) cr3: 0000000630e85000 cr2: 00000000b75ab3f9
> (XEN) ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0000 cs: e008
> (XEN) Xen stack trace from rsp=ffff830631167b68:
> (XEN) ffff830631167bb8 ffff82c4801423a6 0000000131167ba8 ffff830622338000
> (XEN) 0000000000000000 00000000000000e8 0000000000000000 0000000000000003
> (XEN) ffff830622338dc0 ffff830622338000 ffff830631167c18 ffff82c48014268d
> (XEN) ffff830631167bd8 ffff82c480144a04 000000000023368b 0000000000000000
> (XEN) ffff830622338000 00000000000000e8 ffff830622338000 ffff82f60466d160
> (XEN) 0000000000000000 00007d0a00000000 ffff830631167c58 ffff82c48013e6be
> (XEN) ffff830622338018 00000000000000e8 ffff830622338000 0000000000000000
> (XEN) 00000000000000e8 0000000000000000 ffff830631167da8 ffff82c480151905
> (XEN) 0000000000000092 ffff830631167cd0 0000000000000001 ffff82c4802b0880
> (XEN) ffff82c4802c27c0 0000000000000282 ffff830631167ca8 ffff82c480176456
> (XEN) ffff830631167cb8 ffff82c480176601 ffff830631167cf8 ffff82c4801232b4
> (XEN) ffff8306310a0018 ffff830631167e38 0000000000000000 ffff830631167d78
> (XEN) ffff830630e92db0 ffff8300bf4f8000 0000000031167d48 5000000000000000
> (XEN) ffff82f6046e84e0 0000000000237427 5400000000000002 ffff82f6046e84f0
> (XEN) 0000000000000002 0000004844bbac9c ffff82c4802d3ec0 ffff8300bf4f8000
> (XEN) ffff830631167d98 0000000000000282 00000000c8bd98ec 0000000000000001
> (XEN) 0000000000000025 0000000000000000 0000000000000202 fffffffffffffff3
> (XEN) 0000000008064004 0000000000000000 0000000000000000 0000000000000000
> (XEN) ffff830631167ef8 ffff82c480103e41 ffff830631167dc8 0000000000000000
> (XEN) ffff830631167e28 ffff82c48016cc4c ffff830631167e08 0000000180106918
> (XEN) Xen call trace:
> (XEN) [<ffff82c48014725d>] map_vtd_domain_page+0x1d/0x58
> (XEN) [<ffff82c4801423a6>] addr_to_dma_page_maddr+0x151/0x1b7
> (XEN) [<ffff82c48014268d>] intel_iommu_map_page+0x73/0x1db
> (XEN) [<ffff82c48013e6be>] assign_device+0x1e7/0x26a
> (XEN) [<ffff82c480151905>] arch_do_domctl+0x1e9f/0x38aa
> (XEN) [<ffff82c480103e41>] do_domctl+0x1983/0x1a12
> (XEN) [<ffff82c4802111c1>] compat_hypercall+0xa1/0xfa
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 5:
> (XEN) Assertion 'ma < ((((((262UL) >> 8) * 0xffff000000000000UL) | (262UL <<
> 39))) + ((1UL << 39)*10)) - (((((262UL) >> 8) *
> 0xffff00****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|