From: David Greaves <david@dgreaves.com>
To: shemminger@osdl.org, scott.feldman@intel.com
Cc: netdev@oss.sgi.com
Subject: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out
Date: Mon, 14 Jun 2004 17:47:08 +0100 [thread overview]
Message-ID: <40CDD68C.8070509@dgreaves.com> (raw)
Hi
I have 2 machines with Intel/Pro 1000MT cards.
One machine seems to work fine (AFAIK), the other has major problems.
I've swapped the cards and the problem stays on the machine.
I'm using version 5.2.39-k2 from the stock 2.6.6 kernel on both machines.
Any sustained traffic causes repeated:
Jun 14 16:29:14 ash kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 14 16:29:17 ash kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex
Jun 14 16:29:17 ash kernel: nfs: server cu OK
I had a pair of Realtek r8169s that worked fine but only gave me 10Mb/s
so I exchanged them for the Intel/Pro cards in the hope of something
better - now, even with scp's rate limiter as low as 10kb/s this it
still occurs.
I have played with all the module parameters and not found anything that
affects it at 1Gbps
Even dropping to 100Mbps:
Jun 14 17:33:03 ash kernel: e1000: eth0 NIC Link is Up 100 Mbps Full Duplex
Jun 14 17:33:33 ash kernel: NETDEV WATCHDOG: eth0: transmit timed out
it can do 10Mbs:
scp reports a throughput of 1.0Mb/s (... less than thrilling)
however scp now transfers a few Mb and says:
Disconnecting: Corrupted MAC on input.
I found this mail:
http://oss.sgi.com/projects/netdev/archive/2004-06/msg00256.html
from Stephen
which appears to reverse this mail:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107516205706542&w=2
from Scott
which I gather was supposed to correct this problem :)
I have seen no suggestions about other subsystems (eg ACPI etc) that
could also be tried.
David
next reply other threads:[~2004-06-14 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 16:47 David Greaves [this message]
[not found] ` <20040615155111.26d6b809@dell_ss3.pdx.osdl.net>
2004-06-16 10:59 ` 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out David Greaves
2004-06-18 8:04 ` Jens Laas
2004-06-18 9:08 ` 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler David Greaves
2004-06-18 10:27 ` Jens Laas
2004-06-18 12:51 ` David Greaves
2004-06-21 16:42 ` Thayne Harbaugh
2004-06-21 17:29 ` David Greaves
2004-06-21 17:43 ` ganesh.venkatesan
2004-06-21 18:34 ` David Greaves
2004-06-18 18:11 ` 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out Stephen Hemminger
2004-06-18 18:44 ` David Greaves
[not found] ` <20040618141629.0edd9766@dell_ss3.pdx.osdl.net>
2004-06-18 21:28 ` David Greaves
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=40CDD68C.8070509@dgreaves.com \
--to=david@dgreaves.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
--cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).