linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Todor Todorov <ttodorov@web.de>
To: linux-kernel@vger.kernel.org
Subject: eepro100/e100 drivers fragment heavily
Date: Sat, 21 Sep 2002 19:11:26 +0200	[thread overview]
Message-ID: <200209211711.g8LHBQX26908@mailgate5.cinetic.de> (raw)

Hello everyone,

I have a bit of a problem with my Intel based 10/100 pci NIC and kernel 2.4.19, 2.4.20-pre6 and 2.4.20-pre7. I noticed heavy tcp fragmentation when sending data to the network from my linux box. The transfers always stall. The computer is a Dell Inspiron 8000 laptop with an internal Actiontec modem/nic combo pci card based on the Intel Pro chip, running Debian. I observed this behaviour with the eepro100 drivers in 2.4.19, 2.4.20-pre6 and 2.4.20-pre7 and e100 drivers in 2.4.20-pre6 and -pre7. Pulling data from the network is fine and fast though, only sending is a problem.
The only hint I have of what migh be causing the problem is something I read in the specs of my NWAY SOHO switch - it would allow full-duplex 100 MBit/sec only based on auto negotiation, if a nic is in forced mode (say 100 MBit full-duplex), the swith will allow only 100 MBit half-duplex. I tried other high quality switches too, but the result was the same. The other thing worth mentioning is that I have two other servers on the network with pci NICs based on the Realtek RTL 8139 B/D chips and when booting them I always see the message "Setting 100 MBit/sec full-duplex based on auto-negotiation ability". They never have this problem with fragmentation, both pulling and sending data from them is always fast and without any problems. (except when the Dell laptop is involved ;)

So do the eepro100 and e100 drivers have any problem with auto-negotiation? Or does anyone have any other ideas? I'd be glad to run any test you want me to and provide any other information you need, in order to solve this problem.

Thanks in advance.
T.Todorov

______________________________________________________________________________
Jetzt testen für 1 Euro! Ihr All-in-one-Paket! 
https://digitaledienste.web.de/Club/?mc=021106


             reply	other threads:[~2002-09-21 17:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 17:11 Todor Todorov [this message]
2002-09-23 20:03 eepro100/e100 drivers fragment heavily Feldman, Scott

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=200209211711.g8LHBQX26908@mailgate5.cinetic.de \
    --to=ttodorov@web.de \
    --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;
as well as URLs for NNTP newsgroup(s).