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] [PATCH] Fix Maple SMP spurious interrupts assert

To: Amos Waterland <apw@xxxxxxxxxx>
Subject: Re: [XenPPC] [PATCH] Fix Maple SMP spurious interrupts assert
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Fri, 13 Oct 2006 11:44:58 -0400
Cc: Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Oct 2006 08:45:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061012000515.GA9842@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>
References: <20061012000515.GA9842@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
I am not familiar with "SMP spurious interrupts assert"
           panic("Too many (%d) spurrious interrupts in a row\n"
" Known problem, please halt and let machine idle/ cool "
                  "  then reboot\n",
                  100);
message?
That is independent of SMP, we get that in UP as well.
I'm willing to believe that this patch will make it so the panic does not happen.

On Oct 11, 2006, at 8:05 PM, Amos Waterland wrote:

This lets Xen with the SMP patch boot reliably on the Maple-D platform I
have access to.

Sure, I can even run one dom, but at some point my 405 either halts or resets the 970s
at seemingly random points.
I also get:
  PIBS $ Error: Magic number in message area NVRAM is not valid.
  Error: Magic number in message area NVRAM is not valid.
  Error: Magic number in message area NVRAM is not valid.

Which makes me a little woried that we have a wild write somewhere.


I believe that the long-term strategy for Xen/PPC is to completely
virtualize the PIC, but until that happens, this patch will I believe
allow the SMP patch to go in.

I send a suggestion for this patch.. I will attempt that as well.

-JX

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

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