All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@mch.one.pl>
To: linux-kernel@vger.kernel.org
Subject: mass "tulip_stop_rxtx() failed", network stops
Date: Tue, 23 Aug 2005 11:11:58 +0200	[thread overview]
Message-ID: <430AE85E.5040002@mch.one.pl> (raw)

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

and it's filling logs for hours; network doesn't work anymore, and 
someone has to restart the network or the machine itself.

It doesn't always happen with a big traffic - sometimes you can fill the 
100 Mbit link and do lots of reads from the disk, but nothing bad 
happens for hours.


I saw some posts on this issue ("2.6.10-rc3: tulip-driver: 
tulip_stop_rxtx() failed"), but it seemed to me that it wasn't similar 
to my problems; I looked into >2.6.10 kernel changelog, but there were 
no descriptions of that problem, either.


Any help appreciated, because rebooting machines which are 500 km away 
and are not responding is no fun :)


-- 
Tomek
http://wpkg.org


             reply	other threads:[~2005-08-23  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23  9:11 Tomasz Chmielewski [this message]
2005-08-23  9:37 ` mass "tulip_stop_rxtx() failed", network stops jerome lacoste
2005-08-23  9:46   ` Tomasz Chmielewski
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=430AE85E.5040002@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.