[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] xen on hp rx2600


  • To: "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>, "Griffis, Aron" <aron@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Wed, 9 Nov 2005 14:04:42 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 09 Nov 2005 22:07:09 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXld/fO6nYYBodtQzqbs9s75sL/0AAAMNHg
  • Thread-topic: [Xen-ia64-devel] xen on hp rx2600

I think your diagnosis is correct, can't confirm the solution.
One other developer (at CERN) reported this problem months ago.
I think he resolved the problem by turning off the second processor
in firmware.  (I don't recall how, but I think the problem
came back again after upgrading the firmware.)

It's possible that the problem will go away if you turn
on CONFIG_SMP in Xen (xen/include/asm-ia64/config.h).

Tristan, is your dom0 coming up in SMP mode and trying to use
IPI's directly?

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Williamson, Alex (Linux Kernel Dev)
> Sent: Wednesday, November 09, 2005 2:54 PM
> To: Griffis, Aron
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-ia64-devel] xen on hp rx2600
> 
> On Wed, 2005-11-09 at 16:37 -0500, Aron Griffis wrote:
> > I'm trying to bring up xen on hp rx2600, changeset 7d81d6b8c302 from
> > today.  Here is what I'm seeing.  Debugging suggestions?
> > 
> ...
> > (XEN) Boot processor id 0x0/0x0
> > Boot processor id 0x0/0x0
> 
> nosmp option on the dom0 boot parameters maybe?
> 
> > ************* SYSTEM ALERT **************
> > SYSTEM NAME: 
> > 
> > 08 Nov 2005 19:05:07
> > Alert Level 3: Warning
> > Keyword: BOOT_SLAVE_NO_FINAL_WAKEUP_VECTOR
> > Slave wakeup before vector registered
> > Logged by: System Firmware  1
> > Data: Implementation dependent data field
> > 0x7680005B01E002C0 0000000000000001
> > 
> > A: ack read of this entry - X: Disable all future alert messages
> > Anything else skip redisplay the log entry
> > ->Choice:a
> > *****************************************
> 
> This is being generated by the MP.  The current default seems to be
> building a non-SMP xen and running an SMP dom0 kernel on it.  
> Presumably
> you're getting this warning because we sent an IPI to the 2nd CPU to
> wake it up, but firmware has nowhere to send it.
> 
>       Alex
> 
> -- 
> Alex Williamson                             HP Linux & Open Source Lab
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.