From: Tom Sightler <ttsig@tuxyturvy.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: Tom Sightler <ttsig@tuxyturvy.com>,
linux-kernel@vger.kernel.org, arjan@fenrus.demon.nl
Subject: Re: xircom_cb problems
Date: Fri, 08 Jun 2001 21:36:55 -0400 (EDT) [thread overview]
Message-ID: <992050615.3b217db764868@eargle.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106081333090.1029-100000@age.cs.columbia.edu>
In-Reply-To: <Pine.LNX.4.33.0106081333090.1029-100000@age.cs.columbia.edu>
Quoting Ion Badulescu <ionut@cs.columbia.edu>:
> On Fri, 8 Jun 2001, Tom Sightler wrote:
>
> > OK, I tried your patch, it did fix the problem where pump wouldn't
> > pull an IP address, but I'm still having the problem where my ping
> > times go nuts. I've attached an example, it's 100% repeatable on my
> > network at work. It was so bad I couldn't get any benchmark
> numbers.
>
> Just one more question: do you see the same bad ping times if you
> completely comment out the call to set_half_duplex?
No, the problem goes away if I do this, although then I hae the performance
problems as before. I also noticed that even when the call to set_half_duplex
is left in, the switch reports that the link is still in full duplex, 100Mb
mode. I tried forcing half duplex on the switch but this didn't help. It
actually looks like half duplex is not really being set correctly.
I plugged in a desktop with an eepro100 based card and forced the duplex to half
with the command line options and the switch properly reported a half-duplex
link had been negotiated, with the xircom card the switch reports full-duplex
with or without the set_half_duplex line, which certainly implies it's not
really working right.
Hope the helps. I won't be back at the office until Monday so that's the
earliest I'll be able to test again, but I'll be glad to test any combination
that I can.
Later,
Tom
next prev parent reply other threads:[~2001-06-09 1:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 22:49 Linux 2.4.5-ac9 Alan Cox
2001-06-06 2:03 ` Keith Owens
2001-06-06 4:32 ` David Ford
2001-06-06 4:39 ` Jeff Garzik
2001-06-06 4:55 ` David Ford
2001-06-06 5:25 ` Keith Owens
2001-06-06 6:08 ` SCSI is as SCSI don't Alan Olsen
2001-06-06 5:39 ` Greg KH
2001-06-06 8:04 ` Alan Olsen
2001-06-06 6:20 ` Alan Olsen
2001-06-06 7:49 ` Alan Cox
2001-06-07 0:00 ` Alan Olsen
2001-06-06 9:15 ` Linux 2.4.5-ac9 Thomas Sailer
2001-06-06 21:43 ` Alan Cox
2001-06-06 10:51 ` Christoph Hellwig
2001-06-06 11:41 ` Thomas Sailer
2001-06-06 13:40 ` Christoph Hellwig
2001-06-06 14:49 ` Chris Liebman
2001-06-06 17:20 ` Tom Sightler
2001-06-06 21:54 ` Ion Badulescu
2001-06-07 3:30 ` xircom_cb problems Tom Sightler
2001-06-07 8:31 ` Ion Badulescu
2001-06-07 18:40 ` Tom Sightler
2001-06-07 20:29 ` Ion Badulescu
2001-06-08 14:11 ` Tom Sightler
2001-06-08 20:34 ` Ion Badulescu
2001-06-09 1:36 ` Tom Sightler [this message]
2001-06-06 22:44 ` Linux 2.4.5-ac9 arjan
-- strict thread matches above, loose matches on Subject: below --
2001-06-08 17:45 xircom_cb problems Tom Sightler
2001-06-08 17:58 ` Arjan van de Ven
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=992050615.3b217db764868@eargle.com \
--to=ttsig@tuxyturvy.com \
--cc=arjan@fenrus.demon.nl \
--cc=ionut@cs.columbia.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.