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

[Xen-ia64-devel] Re: [Xen-devel] Please pull xen-ia64 bits

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] Re: [Xen-devel] Please pull xen-ia64 bits
From: Haavard Bjerke <havard.bjerke@xxxxxxx>
Date: Mon, 6 Jun 2005 20:40:08 +0200
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Jun 2005 18:39:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD542D5F5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <516F50407E01324991DD6D07B0531AD542D5F5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4i
Using the following cmdline i get output from Xen

append="com1=115200,8n1,0xff5e0000,9 -- console=ttyS0,115200 root=/dev/ sda2"

But it's not looking good:

(XEN) vcpu_ttag: ttag instruction unsupported
(XEN) $$$$$ PANIC in domain 0 (k6=f0000000040a8000): ia64_do_page_fault: 
@0000000000000000??)
(XEN) BUG at domain.c:305
(XEN) $$$$$ PANIC in domain 0 (k6=f0000000040a8000): psr.ic off, delivering 
fault=5300,iip=a0
(XEN) *** ADD REGISTER DUMP HERE FOR DEBUGGING
(XEN) BUG at domain.c:305

The Xenlinux image I'm using works in older Xens.

Haavard

On Mon, Jun 06, 2005 at 08:59:10AM -0700, Magenheimer, Dan (HP Labs Fort 
Collins) wrote:
> There were some changes made recently in core Xen involving
> the serial port.  The latest Xen/ia64 from xeno-unstable.bk
> contains these changes and some additional changes to
> the ia64-specific files to accommodate the core changes. 
> 
> The core changes are very particular about the format
> of the command line -- I'm not sure I fully understand
> yet what variations work and what variations don't work.
> If it doesn't work, there is no way to put out an error
> message (though the core Xen code trys to :-)
> 
> Here's what I think works:  (This will find its way into
> a README file soon.)
> 
> 1) If your machine supports EFI PCDP (I'm told many HP
>    machines do), Xen/ia64 will attempt to read console
>    information directly out of EFI HCDP.  In some cases
>    it can figure out the console, in others it can't.
>    If it can, the command line for Xen should be the
>    same as before, meaning no explicit console... the
>    entire command line is passed to domain0.
> 
>    So your elilo.conf file may have something like this:
> 
> image=xen
>  label=xen
>  initrd=xenlinux
>  read-only
>  append="console=ttyS0,115200 root=/dev/sda2"
> 
> 2) If your machine doesn't support PCDP (or does but
>    Xen can't figure it out), the Xen console must be
>    provided in a very specific format.  The Xen command
>    line is now separated from domain0 in the elilo.conf
>    file using a double-dash:
> 
>       xenarg1 xenarg2 -- dom0arg1 dom0arg2 domarg3
> 
>    The Xen console must be specifed as
>    comX=baud,bits,addr,irq, for example:
> 
>       com1=115200,8n1,0xff5e0000,9
> 
>    This works on my machine.  The following works on
>    another machine with an SMP (management card):
> 
>       com1=115200,8n1,0xf4050000,9
> 
>    So your elilo.conf file may have something like this:
> 
> image=xen
>  label=xen
>  initrd=xenlinux
>  read-only
>  append="com1=115200,8n1,0xff5e0000,9 -- console=ttyS0,115200
> root=/dev/sda2"
> 
>    If you specify any com1= parameter in the Xen part, this
>    overrides any attempt for Xen to try to use PCDP.
> 
>    Note that the irq number will be necessary for keyboard
>    input which doesn't currently work in Xen/ia64 so is
>    a no-op right now.
> 
> 3) If your box is PC-compliant (most Intel boxes I'm told),
>    the default Xen core code may just work...  I don't think
>    any Xen command line needs to be specified.
> 
> This is all brand new so is subject to change. 
> 
> Dan
> 
> > -----Original Message-----
> > From: Haavard Bjerke [mailto:havard.bjerke@xxxxxxx] 
> > Sent: Sunday, June 05, 2005 7:23 AM
> > To: Magenheimer, Dan (HP Labs Fort Collins)
> > Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] Please pull xen-ia64 bits
> > 
> > I've lost console output from the hypervisor with this latest 
> > bk pull. Is this because of the latest serial work? I tried 
> > changing the command line to append="comx=115200 console=comx 
> > -- nomca console=tty0 console=ttyS0,115200 root=/dev/sda2 " 
> > with x in 0 through 2, but no dice. I've also tried 
> > "com2=57600,8n1 console=com2". The cmd line that worked 
> > before, was "nomca console=tty0 console=ttyS0,115200 root=/dev/sda2".
> > 
> > Dom0 still works as before.
> > 
> > Haavard
> > 
> > On Fri, Jun 03, 2005 at 08:25:23AM -0700, Magenheimer, Dan 
> > (HP Labs Fort Collins) wrote:
> > > A couple more fixes for the recent include file cleanup
> > > (when CONFIG_VTI is on) and one fix for the recent cpumask
> > > cleanup.
> > > 
> > > Please pull:
> > > bk://xen-ia64.bkbits.net/xeno-unstable-ia64.bk
> > > 
> > > Thanks,
> > > Dan 
> > > 
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> > 

-- 
Håvard K. F. Bjerke
http://www.idi.ntnu.no/~havarbj/

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

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