From: Steve Simitzis <steve@saturn5.com>
To: linux-kernel@vger.kernel.org
Subject: e1000 problems in 2.6.x
Date: Sat, 14 Feb 2004 03:13:49 -0800 [thread overview]
Message-ID: <20040214111349.GC1040@saturn5.com> (raw)
hello. since upgrading to 2.6 from 2.4.22, my e1000 devices have
been angry. i've tried running both 2.6.2 and 2.6.3-rc2, but the
results have been the same. when i return to 2.4.22, all of the
problems go away.
i'm getting these over and over again:
Feb 11 19:57:55 sg1 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Feb 11 19:57:57 sg1 kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex
Feb 11 19:58:17 sg1 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Feb 11 19:58:18 sg1 kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex
i'm also seeing about 10-20% of my RX packets as errors when running 2.6.x,
and 0 errors when running 2.4.22.
another oddity is that even after forcing my interfaces to 100 Mbps
full duplex, my switch is reporting half duplex. again, this only happens
in 2.6.x. when running 2.4.22, full duplex is properly negotiated between
the e1000 and my switch.
i tried turning off TSO, as suggested elsewhere by Scott Feldman, but that
had no effect.
i would love to run 2.6, so if there's anything else i can try (or if
this is a known problem and about to be fixed), please let me know.
thanks in advance.
:)
--
steve simitzis : /sim' - i - jees/
pala : saturn5 productions
www.steve.org : 415.282.9979
hath the daemon spawn no fire?
next reply other threads:[~2004-02-14 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 11:13 Steve Simitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 0:26 e1000 problems in 2.6.x Feldman, Scott
2004-02-15 2:32 ` Steve Simitzis
2004-02-15 3:22 ` Bill Davidsen
2004-02-15 3:53 ` Steve Simitzis
2004-02-15 15:20 Re[2]: " Klaus Dittrich
2004-02-16 1:14 ` Re[3]: " Elikster
2004-02-16 2:12 ` Steve Simitzis
2004-02-16 4:17 Paul Blazejowski
2004-02-17 18:26 ` Anton Blanchard
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=20040214111349.GC1040@saturn5.com \
--to=steve@saturn5.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