Messages in this thread | | | Date | Tue, 23 Aug 2005 11:46:26 +0200 | From | Tomasz Chmielewski <> | Subject | Re: mass "tulip_stop_rxtx() failed", network stops |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |