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

Re: [XenPPC] vcpu-list panic

To: Amos Waterland <apw@xxxxxxxxxx>
Subject: Re: [XenPPC] vcpu-list panic
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Wed, 06 Sep 2006 14:56:53 -0500
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Sep 2006 12:56:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060906184432.GA20533@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <20060906184432.GA20533@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2006-09-06 at 14:44 -0400, Amos Waterland wrote:
> Using current xen.hg and linux.hg, I get this when I try to 
> run `xm vcpu-list':
> 
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) paddr_to_maddr: Dom:0 paddr: 0xf5d5ecc0 bad type:0x3
> (XEN) ****************************************
> (XEN) 
> (XEN) Reboot in five seconds...
> 
> Note that `xm list' works fine.  The 0xf5d5ecc0 address is consistent
> across boots.

I see the same thing. The backtrace is:
#0  panic (fmt=0x456d10 "%s: Dom:%d paddr: 0x%lx bad type:0x%x\n")
    at console.c:610
#1  0x00000000004459bc in paddr_to_maddr (paddr=0xf6fb7278) at usercopy.c:65
#2  0x000000000044619c in xencomm_handle_is_null (ptr=0xf6fb7278)
    at usercopy.c:265
#3  0x0000000000401c58 in cpumask_to_xenctl_cpumap (xenctl_cpumap=0xfaa8,
    cpumask=0xb7e178) at domctl.c:36
#4  0x0000000000403348 in do_domctl (u_domctl={__pad = 0xfc20, p = 0x7d04000})
    at domctl.c:396
#5  0x00000000004373c4 in hcall_xen (num=0x24, regs=0xfd90) at hcalls.c:76
#6  0x00000000004374e0 in do_hcall (regs=0xfd90) at hcalls.c:104
#7  0x0000000000449d34 in ex_hcall_continued () at misc.h:31

I'll check it out.

-- 
Hollis Blanchard
IBM Linux Technology Center


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

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