From: Petr Sebor <petr@scssoft.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Date: Fri, 23 Jan 2004 22:43:14 +0100 [thread overview]
Message-ID: <40119572.5020403@scssoft.com> (raw)
Hello,
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
then its working ok again, until the next watchdog message.
It has happened even before the cabling upgrade, it was just very rare.
I have tried kernels 2.6.0, 2.6.1, 2.6.2-bk1 and it happens all the
time. It is just that is _seems_ to happen more often with the 2.6.2-bk
The machine in question is an Opteron 244 based server (though kernel
is compiled for 32bits/Athlon). SMP kernel makes no difference, it will
eventually happen as well. The server is not heavily loaded... only few
users
can trigger the issue. Board is MSI KT800 based.
I have tried to switch NICs, but there is no difference. Onboard
integrated TG3
gigabit network controller suffers the '100% CPU usage' issue when
utilized so
this unfortunately no option at the moment.
Anyone having a clue what might be wrong here?
Have a nice weekend,
Petr
next reply other threads:[~2004-01-23 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 21:43 Petr Sebor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 22:28 [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out Feldman, Scott
2004-01-24 19:36 ` Sergey S. Kostyliov
2004-01-26 10:33 ` Petr Sebor
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01036EA9DA@orsmsx402.jf.intel.com>
2004-01-27 0:37 ` Feldman, Scott
2004-01-27 13:59 ` Petr Sebor
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=40119572.5020403@scssoft.com \
--to=petr@scssoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox