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/
Home Products Support Community News


[Xen-devel] Network stops responding after some time

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Network stops responding after some time
From: Adnan Khaleel <adnan@xxxxxxxxxx>
Date: Mon, 24 Jul 2006 13:49:31 -0500
Cc: Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Wed, 26 Jul 2006 02:38:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Reply-to: adnan@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I need help in trying to understand why the ethernet driver has locked up and 
how I can go about outputting debug messages. I see in /proc/interrrupts that 
the interrupt count of eth0 just stops incrementing. I've tried different 
(3Com, Realtek 8169, Realtek 8139) based network cards and this happens with 
all. I'm not sure what is so unique about my system that might be causing this 
to lockup, its a regular Nforce3 based system with 512MB ram. This problem does 
not happen if I'm not using a Xen enabled kernel. This is entirely happening in 
dom0 and there aren't any user domains so its not a bridging issue. I've also 
disabled the Xen backend drivers (netbk.ko and netloop.ko) so its talking to 
the network chip directly. 

Any help? Please? 


Xen-devel mailing list

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