From: Willy Tarreau <w@1wt.eu>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
netdev@vger.kernel.org, dmpesl <dmpesl@ldis.cs.msu.su>
Subject: FWD: 2.4.35 e1000 problems
Date: Mon, 15 Oct 2007 15:59:17 +0200 [thread overview]
Message-ID: <20071015135917.GA9608@1wt.eu> (raw)
Hi,
Dmitry, I've forwarded your mail to the netdev mailing list and to
the e1000 maintainers.
Auke, does it sound like a known problem ? Maybe someone has seen it
in 2.6 ? Just for the record, e1000 in 2.4.35 is 7.3.20-k4.
Dmitry, if you have time for a test, I think it would be good if you
could test the most recent driver from e1000.sf.net. It might give
us some more information about the problem's cause. Otherwise, let's
wait for Auke's advices and/or questions.
Regards,
Willy
----- Forwarded message from dmpesl <dmpesl@ldis.cs.msu.su> -----
Date: Mon, 15 Oct 2007 17:54:01 +0400 (MSD)
From: dmpesl <dmpesl@ldis.cs.msu.su>
Subject: 2.4.35 e1000 problems
To: w@1wt.eu
X-X-Sender: dmpesl@ldisi.cs.msu.su
Hello, Willy
on recent month i've changed kernel from 2.4.31->2.4.35 on my Owl-based
web server (purchased SATA hdd, onboard SATA 20378), Asus PCH-DR mb,
2*Xeon, and noticed that following error occurs on network card:
---------------------------------------------
Sep 29 21:29:51 host kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 21:29:53 host kernel: e1000: eth0: e1000_watchdog: NIC Link is Up
100 Mbps Full Duplex, Flow Control: RX/TX
Sep 29 22:28:03 host kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 22:28:05 host kernel: e1000: eth0: e1000_watchdog: NIC Link is Up
100 Mbps Full Duplex, Flow Control: RX/TX
Sep 30 00:51:35 host kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 30 00:51:37 host kernel: e1000: eth0: e1000_watchdog: NIC Link is Up
100 Mbps Full Duplex, Flow Control: RX/TX
---------------------------------------------
After some conversation with my collocation provider (changing cables and
switch port) i've searched google to same errors and found some advises to
use ethtool -k tso off, but this is not work with my kernel/distribution.
Then i swapped just e1000 driver in 2.4.35 to older, from 2.4.31.
Now everything works, without loosing link.
Regards, Dmitry
----- End forwarded message -----
next reply other threads:[~2007-10-15 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 13:59 Willy Tarreau [this message]
2007-10-15 14:25 ` FWD: 2.4.35 e1000 problems dmpesl
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=20071015135917.GA9608@1wt.eu \
--to=w@1wt.eu \
--cc=auke-jan.h.kok@intel.com \
--cc=dmpesl@ldis.cs.msu.su \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).