From: Tomasz Chmielewski <mangoo@mch.one.pl>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: mass "tulip_stop_rxtx() failed", network stops
Date: Tue, 23 Aug 2005 11:46:26 +0200 [thread overview]
Message-ID: <430AF072.2060908@mch.one.pl> (raw)
In-Reply-To: <5a2cf1f6050823023741682524@mail.gmail.com>
jerome lacoste schrieb:
> On 8/23/05, Tomasz Chmielewski <mangoo@mch.one.pl> wrote:
>
>>We are running almost 20 Fujitsu-Siemens Scenic machines, 2.6.8.1
>>kernel, equipped with a onboard card that uses a tulip module:
>>
>>02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
>>Ethernet 10/100 (rev 11)
>>
>>No problem with those.
>>
>>
>>We are running four more machines like that, the only difference is the
>>kernel they are running (2.6.11.4).
>>
>>On some of them, there are serious problems with a network, and they
>>usually happen when the traffic is bigger than usual (i.e., some big
>>software deployment to several workstations, remote backup, etc.).
>>
>>The syslog is then full of entries like that:
>>
>>Aug 21 04:04:30 SERVER-B-HS kernel: NETDEV WATCHDOG: eth0: transmit
>>timed out
>>Aug 21 04:04:30 SERVER-B-HS kernel: 0000:00:06.0: tulip_stop_rxtx() failed
>
>
> I am seeing thousands of tulip_stop_rxtx() failed messages as well
> with 2.6.11. No regular network failure though.
>
> See http://kerneltrap.org/mailarchive/1/message/110291/flat
Lucky you.
Really no network problems, no increased ping responses?
For me lots of pings are lost, and when this "tulip_stop_rxtx() failed"
happens, the time for a ping to "go back" can be as big as 14 seconds in
a 100 Mbit LAN.
--
Tomek
http://wpkg.org
next prev parent reply other threads:[~2005-08-23 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 9:11 mass "tulip_stop_rxtx() failed", network stops Tomasz Chmielewski
2005-08-23 9:37 ` jerome lacoste
2005-08-23 9:46 ` Tomasz Chmielewski [this message]
2005-08-23 10:11 ` Tomasz Chmielewski
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=430AF072.2060908@mch.one.pl \
--to=mangoo@mch.one.pl \
--cc=linux-kernel@vger.kernel.org \
/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.