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 stops responding after some time

To: <adnan@xxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Network stops responding after some time
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 28 Jun 2006 00:09:20 +0100
Delivery-date: Tue, 27 Jun 2006 16:09:43 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaOzn+peRL5bF2CRZCrts5MQw3bDwLb8iAw
Thread-topic: [Xen-devel] Network stops responding after some time
 
> I'm using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on 
> X86-64 and I'm experiencing a problem with the network.
> I boot into the Xen kernel and everything works just fine. I 
> can browse the net etc.
> However after a while the network stops responding 
> completely. I am not sure what causes this to happen or what 
> triggers it. After a few hours, the network just stops working.
> 
> Doing an ifconfig -a before and after gives me the following
> 
> Before
> eth0      Link encap:Ethernet  HWaddr 00:0D:61:42:F5:8D  
>           inet addr:172.18.41.82  Bcast:172.18.43.255  
> Mask:255.255.252.0
>           inet6 addr: fe80::20d:61ff:fe42:f58d/64 Scope:Link
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500 
>  Metric:1
>           RX packets:278 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
> After
> eth0      Link encap:Ethernet  HWaddr 00:0D:61:42:F5:8D  
>           inet addr:172.18.41.82  Bcast:172.18.43.255  
> Mask:255.255.252.0
>           inet6 addr: fe80::20d:61ff:fe42:f58d/64 Scope:Link
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500 
>  Metric:1
>           RX packets:192846 errors:0 dropped:15431 overruns:0 frame:0
>           TX packets:2268 errors:0 dropped:506 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:29687820 (28.3 Mb)  TX bytes:324494 (316.8 Kb)
>           Interrupt:19 Base address:0x8000 

> I am not sure what else would be helpful in diagnosing the 
> problem. Does anybody has any ideas on what else I should be checking?

Are these stats from dom0 before starting xend?

The dropped counts in eth0 suggest the ethernet device driver has locked
up. My bet would be that the interrupt count stops going up (see
/proc/interrupts).

Compare the irq number between the xen and normal kernels. In fact, diff
the boot messages to check the same irq routeing etc is happening.

Ian

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