All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: network dropouts
Date: Fri, 17 Dec 2004 21:25:52 +0100	[thread overview]
Message-ID: <41C340D0.2080904@fzu.cz> (raw)
In-Reply-To: <E1CfOMu-0007r3-00@mta1.cl.cam.ac.uk>

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

  reply	other threads:[~2004-12-17 20:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12 20:34 network dropouts Jan Kundrát
2004-12-13 20:08 ` Jan Kundrát
2004-12-14 11:04   ` Ian Pratt
2004-12-14 11:27     ` Jan Kundrát
2004-12-14 11:36       ` Keir Fraser
2004-12-17 18:37         ` Jan Kundrát
2004-12-17 20:06           ` Keir Fraser
2004-12-17 20:25             ` Jan Kundrát [this message]
2004-12-17 20:54               ` Keir Fraser
2004-12-17 21:03                 ` Jan Kundrát
2004-12-17 21:18                   ` Jan Kundrát
2004-12-17 20:36             ` Jan Kundrát
2004-12-15 14:58       ` Jan Kundrát
2004-12-14 16:43     ` Nivedita Singhvi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41C340D0.2080904@fzu.cz \
    --to=jan.kundrat@fzu.cz \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.