From: "Sergey S. Kostyliov" <rathamahata@php4.ru>
To: "Feldman, Scott" <scott.feldman@intel.com>,
"Petr Sebor" <petr@scssoft.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.x] e1000: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sat, 24 Jan 2004 22:36:03 +0300 [thread overview]
Message-ID: <200401242236.03765.rathamahata@php4.ru> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102229D92@orsmsx402.jf.intel.com>
Hello Scott, Petr,
On Saturday 24 January 2004 01:28, 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.
I have had exactly the same problem with 2.6.{0,1} kernels:
"NETDEV WATCHDOG: eth0: transmit timed out"
where eth0 is:
"03:07.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)".
The only difference is that my eth0 is at 100 Mbps Full Duplex.
And yes, in my case this problem was solved by `ethtool -K eth0 tso off`.
>
> -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/
--
Best regards,
Sergey S. Kostyliov <rathamahata@php4.ru>
Public PGP key: http://sysadminday.org.ru/rathamahata.asc
next prev parent reply other threads:[~2004-01-24 19:36 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 [this message]
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
-- 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=200401242236.03765.rathamahata@php4.ru \
--to=rathamahata@php4.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@scssoft.com \
--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