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] Serial woes with kexec on an HP RX2620

To: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Serial woes with kexec on an HP RX2620
From: Simon Horman <horms@xxxxxxxxxxxx>
Date: Wed, 23 May 2007 12:49:56 +0900
Cc: Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 22 May 2007 20:48:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r804 (Debian)
Hi,

I've been trying to hunt down a problem with the serial console on the
HP RX2620, whereby after kexec the console doesn't accept input,
although it does produce output quite happily. I should also note that
this problem does not manifest on the Tiger2 machine I have.

I've been puzzling over this for a while now, and it seems like
no RX interrupts are generated. Though I can't fathom why. If
I force the serial driver into polling mode (with some handy #if 0 work)
then everything is fine - well as fine as a polling driver can be.

I have tried comparing the serial setup in the xen and linux drivers,
however the implementation is quite different, making comparisons
difficult at best. I have tried seeing which of the many work
arounds contained in the linux driver are activated when it is used,
however it seems that the answer is none, or in other words,
the linux driver doesn't seem to do anything sepcial.

I'll continue looking over this, but if anyone has any ideas I
would be most grateful.

For reference, I am using the following kexec for ia64 on xen patches
(largely written by myself)

http://www.vergenet.net/linux/kexec/ia64-xen/20070417/

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


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