From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Jan_Kundr=E1t?= Subject: Re: network dropouts Date: Fri, 17 Dec 2004 21:25:52 +0100 Message-ID: <41C340D0.2080904@fzu.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: Ian Pratt , xen-devel List-Id: xen-devel@lists.xenproject.org > Your syslog entries make it look like your eth0 carrier was out for > one minute, but the thing to do is to observe the times at which you > get outages, and see what syslog messages you get at those times -- > are you getting NETDEV_CHANGE messages at those points in time? Originally, I thought that I got outage only if network is idle for some time, but right now, I typed `dmesg` in the ssh connection, it showed the log and then freezed (network, not machine). After a while, it get ok. According to syslog messages, network drops out for exactly one minute. It hapens quite often (`grep forwarding /var/log/messages`): Dec 17 15:56:17 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 18:38:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 19:35:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 19:42:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:01:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:17:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:24:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:36:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:43:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 20:53:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 21:01:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 21:11:02 zirafa xen-br0: port 1(eth0) entering forwarding state Dec 17 21:19:02 zirafa xen-br0: port 1(eth0) entering forwarding state > And maybe your switch is good, but 3c590 *is* an ancient p.o.s. ;-) Well, comparing it to rtl-8139 based cards, I think 3com is better, IMHO ;-). All the eepro cards are in more important machines... So, do you think that the problem is in the NIC? `ifconfig` says "carrier: 0"... I could replace it with some Realtek-based card. Is there anything else I can do? TIA, jkt -- cd /local/pub && more beer > /dev/mouth ------------------------------------------------------- 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/