content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Date: Fri, 23 Jan 2004 14:28:36 -0800
Message-ID: <C6F5CF431189FA4CBAEC9E7DD5441E0102229D92@orsmsx402.jf.intel.com>
Thread-Topic: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Thread-Index: AcPh+p0ZLtJ0cujJSy2EzaaQtXQVKgABWmUA
From: "Feldman, Scott" <scott.feldman@intel.com>
To: "Petr Sebor" <petr@scssoft.com>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 893
Lines: 24

> since we have upgraded cabling on our network and transfer 
> speeds increased a little bit, we are experiencing very often 
> situations where the Intel PRO/1000 nics just stop responding 
> and network dies for a while. Local console works, there are 
> no more error messages other than (when the eth0 comes to a 
> life again):
> 
> NETDEV WATCHDOG: eth0: transmit timed out
> e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex

Petr, I need you to try something.  Get ethtool 1.8
(sf.net/projects/gkernel) and turn off TSO:

  # ethtool -K eth0 tso off

If you now longer see NETDEV WATCHDOG's, I have a next step.  More on
that later.

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