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-ia64-devel

Re: [Xen-ia64-devel] [PATCH 0/6] [P2M/VP step 4]

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH 0/6] [P2M/VP step 4]
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Fri, 12 May 2006 11:28:50 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 May 2006 10:29:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060512112214.GA1740%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: LOSL
References: <20060512112214.GA1740%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006-05-12 at 20:22 +0900, Isaku Yamahata wrote:
> Subject: [PATCH 1/6] [P2M/VP step 4] xen: balloon driver support
> Subject: [PATCH 2/6] [P2M/VP step 4] xen: remove dom0vp_populate_physmap 
> hypercall
> Subject: [PATCH 3/6] [P2M/VP step 4] linux: remove dom0vp_populate_physmap 
> hypercall
> Subject: [PATCH 4/6] [P2M/VP step 4] xen: fix vmx_build_physmap_table()
> Subject: [PATCH 5/6] [P2M/VP step 4] xen: implemanted domain destruction again
> Subject: [PATCH 6/6] [P2M/VP step 4] xen: remove mm_struct::pt_list

   Applied.  There seems to be a regression in VTi though.  I'm no
longer able to boot a VTi domain.  I get the following:

(XEN) ### domain f0000000041750c8: rid=c0000-100000 mp_rid=3000
(XEN) arch_domain_create: domain=f0000000041750c8
(XEN) vpd base: 0xf0000000042e0000, vpd size:65536
(XEN) Allocate domain vhpt at 0xf000000153000000
(XEN) Allocate domain vtlb at 0xf000000154e00000
(XEN) ivt_base: 0xf000000004010000
(XEN) VMX domain bind port -1 to vcpu 0 failed!
(XEN) domain_crash_sync called from vmx_init.c:435
(XEN) Domain 2 (vcpu#0) crashed on cpu#5:
(XEN) d 0xf0000000041750c8 domid 2
(XEN) vcpu 0xf0000000043b0000 vcpu 0
(XEN) 
(XEN) CPU 5
(XEN) psr : 0000501008826008 ifs : 8000000000000000 ip  : [<80000000ffffffb0>]
(XEN) ip is at ???
(XEN) unat: 0000000000000000 pfs : 0000000000000000 rsc : 0000000000000000
(XEN) rnat: 0000000000000000 bsps: 0000000000000000 pr  : 0000000000000000
(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
(XEN) csd : 0000000000000000 ssd : 0000000000000000
(XEN) b0  : 0000000000000000 b6  : 0000000000000000 b7  : 0000000000000000
(XEN) f6  : 000000000000000000000 f7  : 000000000000000000000
(XEN) f8  : 000000000000000000000 f9  : 000000000000000000000
(XEN) f10 : 000000000000000000000 f11 : 000000000000000000000
(XEN) r1  : 0000000000000000 r2  : 0000000000000000 r3  : 0000000000000000
(XEN) r8  : 0000000000000000 r9  : 0000000000000000 r10 : 0000000000000000
(XEN) r11 : 0000000000000000 r12 : 0000000000000000 r13 : 0000000000000000
(XEN) r14 : 0000000000000000 r15 : 0000000000000000 r16 : 0000000000000000
(XEN) r17 : 0000000000000000 r18 : 0000000000000000 r19 : 0000000000000000
(XEN) r20 : 0000000000000000 r21 : 0000000000000000 r22 : 0000000000000000
(XEN) r23 : 0000000000000000 r24 : 0000000000000000 r25 : 0000000000000000
(XEN) r26 : 0000000000000000 r27 : 0000000000000000 r28 : 0000000000000000
(XEN) r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
(XEN) 
(XEN) Call Trace:
(XEN)  [<f000000004089480>] show_stack+0x80/0xa0
(XEN)                                 sp=f0000000043b7c30 bsp=f0000000043b0d98
(XEN)  [<f00000000401fcc0>] __domain_crash+0xe0/0x110
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d70
(XEN)  [<f00000000401fd10>] __domain_crash_synchronous+0x20/0x50
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d58
(XEN)  [<f0000000040775d0>] vmx_do_launch+0x200/0x210
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d30
(XEN)  [<f00000000405ea90>] schedule_tail+0x80/0x120
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d10
(XEN)  [<f0000000040885a0>] ia64_invoke_schedule_tail+0x20/0x40
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0cc0
(XEN) ### domain f0000000041750c8: rid=c0000-100000 mp_rid=3000
(XEN) arch_domain_create: domain=f0000000041750c8
(XEN) vpd base: 0xf0000000042e0000, vpd size:65536
(XEN) Allocate domain vhpt at 0xf000000138000000
(XEN) Allocate domain vtlb at 0xf000000139c00000
(XEN) ivt_base: 0xf000000004010000
(XEN) VMX domain bind port -1 to vcpu 0 failed!
(XEN) domain_crash_sync called from vmx_init.c:435
(XEN) Domain 3 (vcpu#0) crashed on cpu#5:
(XEN) d 0xf0000000041750c8 domid 3
(XEN) vcpu 0xf0000000043b0000 vcpu 0
(XEN) 
(XEN) CPU 5
(XEN) psr : 0000501008826008 ifs : 8000000000000000 ip  : [<80000000ffffffb0>]
(XEN) ip is at ???
(XEN) unat: 0000000000000000 pfs : 0000000000000000 rsc : 0000000000000000
(XEN) rnat: 0000000000000000 bsps: 0000000000000000 pr  : 0000000000000000
(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
(XEN) csd : 0000000000000000 ssd : 0000000000000000
(XEN) b0  : 0000000000000000 b6  : 0000000000000000 b7  : 0000000000000000
(XEN) f6  : 000000000000000000000 f7  : 000000000000000000000
(XEN) f8  : 000000000000000000000 f9  : 000000000000000000000
(XEN) f10 : 000000000000000000000 f11 : 000000000000000000000
(XEN) r1  : 0000000000000000 r2  : 0000000000000000 r3  : 0000000000000000
(XEN) r8  : 0000000000000000 r9  : 0000000000000000 r10 : 0000000000000000
(XEN) r11 : 0000000000000000 r12 : 0000000000000000 r13 : 0000000000000000
(XEN) r14 : 0000000000000000 r15 : 0000000000000000 r16 : 0000000000000000
(XEN) r17 : 0000000000000000 r18 : 0000000000000000 r19 : 0000000000000000
(XEN) r20 : 0000000000000000 r21 : 0000000000000000 r22 : 0000000000000000
(XEN) r23 : 0000000000000000 r24 : 0000000000000000 r25 : 0000000000000000
(XEN) r26 : 0000000000000000 r27 : 0000000000000000 r28 : 0000000000000000
(XEN) r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
(XEN) 
(XEN) Call Trace:
(XEN)  [<f000000004089480>] show_stack+0x80/0xa0
(XEN)                                 sp=f0000000043b7c30 bsp=f0000000043b0d98
(XEN)  [<f00000000401fcc0>] __domain_crash+0xe0/0x110
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d70
(XEN)  [<f00000000401fd10>] __domain_crash_synchronous+0x20/0x50
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d58
(XEN)  [<f0000000040775d0>] vmx_do_launch+0x200/0x210
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d30
(XEN)  [<f00000000405ea90>] schedule_tail+0x80/0x120
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0d10
(XEN)  [<f0000000040885a0>] ia64_invoke_schedule_tail+0x20/0x40
(XEN)                                 sp=f0000000043b7e00 bsp=f0000000043b0cc0

Anthony and Kevin, can you help to get this working again?  Thanks,

        Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


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

<Prev in Thread] Current Thread [Next in Thread>