From: Petr Sebor <petr@scssoft.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Date: Mon, 26 Jan 2004 11:33:05 +0100 [thread overview]
Message-ID: <4014ECE1.1090602@scssoft.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102229D92@orsmsx402.jf.intel.com>
Feldman, Scott wrote:
>>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
>
>
Scott,
after a weekend and half of working day (with extra torturing of the
network card)
the NETDEV WATCHDOG's are not barking anymore with the tso's disabled.
Do you want me to do more testing or will you tell me what _the_ next
step is ? :-)
Regards,
Petr
next prev parent reply other threads:[~2004-01-26 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01036EA9DA@orsmsx402.jf.intel.com>
2004-01-27 0:37 ` Feldman, Scott
2004-01-27 13:59 ` Petr Sebor
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 21:43 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=4014ECE1.1090602@scssoft.com \
--to=petr@scssoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/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