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 dropouts

To: Jan Kundrát <jan.kundrat@xxxxxx>
Subject: Re: [Xen-devel] network dropouts
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 14 Dec 2004 11:36:00 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 14 Dec 2004 11:37:20 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 14 Dec 2004 12:27:52 +0100." <41BECE38.2030804@xxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> no, I'm setting it manually via `ifconfig` in init script. Notice the 
> following lines in kernel log:
> 
> Dec 12 20:33:23 zirafa xen-br0: port 1(eth0) entering disabled state
> Dec 12 20:34:23 zirafa xen-br0: port 1(eth0) entering learning state
> 
> Why is eth0 (the only physical device in xen-br0) getting into disabled 
> state?

My guess would be that the bridge code is receiving carrier-change
events from eth0. This causes it to put eth0 in disabled state for a
while. 

One way to check this would be to add some printk()'s to
net/bridge/br_notify.c and see whether you are getting NETDEV_CHANGE
or NETDEV_DOWN events. If so, it may be that your physical connection,
or your router/switch/hub, is a bit dodgy.

None of the other paths via which the interface may get disabled seem
very likely to occur, but we can look at those if it doesn't appear
that you are getting NETDEV events.

 -- Keir


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel