linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Feldman, Scott" <scott.feldman@intel.com>
To: "'Todor Todorov'" <ttodorov@web.de>, linux-kernel@vger.kernel.org
Subject: RE: eepro100/e100 drivers fragment heavily
Date: Mon, 23 Sep 2002 13:03:58 -0700	[thread overview]
Message-ID: <288F9BF66CD9D5118DF400508B68C446047589DF@orsmsx113.jf.intel.com> (raw)

Todor Todorov wrote:

> 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. 

Please confirm that the switch and nic are both set to auto-neg, or both the
switch and the nic forced to the same settings (i.e. 100/half).  We need to
make sure both ends of the wire match.

-scott

             reply	other threads:[~2002-09-23 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 20:03 Feldman, Scott [this message]
2002-09-24 16:06 ` AW: eepro100/e100 drivers fragment heavily Todor Todorov
  -- strict thread matches above, loose matches on Subject: below --
2002-09-21 17:11 Todor Todorov

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=288F9BF66CD9D5118DF400508B68C446047589DF@orsmsx113.jf.intel.com \
    --to=scott.feldman@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttodorov@web.de \
    /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).