netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Wolfgang Nothdurft <Wolfgang.Nothdurft@linogate.de>
Cc: netdev@vger.kernel.org
Subject: Re: 2.4.35-pre1: new e1000 driver breaks old hardware
Date: Fri, 15 Jun 2007 08:53:33 -0700	[thread overview]
Message-ID: <4672B5FD.7070304@intel.com> (raw)
In-Reply-To: <46723F39.1000808@linogate.de>

Wolfgang Nothdurft wrote:
> Hi,
> 
> with the new e1000 driver version 7.3.20 the onboard gigabit nic 82547EI
> (8086:1019) doesn't work correctly.
> After transferring about 100 megabytes over a gigabit link the transfer
> stopped and I have to reinit the link either by doing a ifconfig down/up
> or unplugging the network cable.
> The RxIntDelay is set to 0 like described in the docu. Playing with this
> Parameter only increases the amount of traffic to be send and the error
> occurs later.

have you tried (the default) 8000 ? Do you get the same problem when you run 
2.6.21 with 7.5.5.1 or 7.3.20 ?

> This happens also with the 7.4.35 and 7.5.5 driver from the intel side.
> The driver 5.7.6 from kernel 2.4.33.3 and the 6.1.16 from intel works
> very well on this hardware.
> Also other gigabit nics we use didn't have this problem.
> Is this issue already known?

this is the first time I have heard this issue.

> Is there any solution yet?

I'm not that good :)

Can you file a bugreport on e1000.sf.net and attach the usual (ethtool -e, 
dmesg, ifconfig -a, lspci -vv) debugging output and problem description for us? 
I'll try to see if I can have our labs setup a repro case, which might be hard 
given the adapter type, but we will do our best.

Auke

  reply	other threads:[~2007-06-15 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  7:26 2.4.35-pre1: new e1000 driver breaks old hardware Wolfgang Nothdurft
2007-06-15 15:53 ` Kok, Auke [this message]
2007-06-19 10:30   ` Wolfgang Nothdurft
2007-08-14  8:53   ` Wolfgang Nothdurft

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=4672B5FD.7070304@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=Wolfgang.Nothdurft@linogate.de \
    --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).