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

Re: [Xen-devel] network (irq?) problems in unstable

To: Gerd Knorr <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] network (irq?) problems in unstable
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 30 May 2005 14:36:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 30 May 2005 13:32:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050530125247.GA12140@bytesex>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050530125247.GA12140@bytesex>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 30 May 2005, at 13:52, Gerd Knorr wrote:

With xen unstable I have the problem that the network stops
working after a while.  Heavy network traffic seems to make it
more likely, it triggers almost every time I try to untar a
kernel source tree, where the tarball comes from a NFS-mounted
volume.

The network card doesn't receive interrupts any more according
to /proc/interrupts.  It works fine in native linux and also
with xen 2.0.  It's a tulip card.  Anyone has an idea what this
might be or where to look?

The new IRQ code in unstable is not so well tested on non-ACPI and non-IOAPIC systems (most of our boxes are SMP servers). May be worth looking at boot-time output of Xen vs. native Linux. Also, particularly if you have a null modem cable attached, add tracing on a debug key to see what Xen thinks the status of each IRQ line is (disabled, in_progress, etc.). Managing IRQ lines via legacy PIC is pretty straightforward so this can't really be that hard a bug to fix I think (hope). :-)

 -- Keir


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