public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Paul Blazejowski <paulb@blazebox.homeip.net>, scott.feldman@intel.com
Cc: steve@saturn5.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: e1000 problems in 2.6.x
Date: Wed, 18 Feb 2004 05:26:46 +1100	[thread overview]
Message-ID: <20040217182645.GA22534@krispykreme> (raw)
In-Reply-To: <1076905069.4092.4.camel@blaze.homeip.net>

 
Hi,

> I am experiencing same problem with e1000 on 2.6.3-rc2-mm1 and all
> previous 2.6 kernels with getting the transmit timed out messages.I do
> not get the transmission errors though.The same setup works fine on 2.4
> kernel just like yours.

We beat a recent 2.6 up with specweb on ppc64 and got the transmit
timeout errors within about 30 seconds. Disabling TSO made the problem
go away. (I actually hacked the driver forgetting we can do it via
ethtool these days).

Scott: it smells like the TSO early write back issue, perhaps the new
version of the fix isnt working properly. I need to verify that turning
TSO on/off via ethtool has the same effect.

Anton

  reply	other threads:[~2004-02-17 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16  4:17 e1000 problems in 2.6.x Paul Blazejowski
2004-02-17 18:26 ` Anton Blanchard [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-15  0:26 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-14 11:13 Steve Simitzis

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=20040217182645.GA22534@krispykreme \
    --to=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulb@blazebox.homeip.net \
    --cc=scott.feldman@intel.com \
    --cc=steve@saturn5.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