From: Jordan Mendelson <jordy@napster.com>
To: Daniel Walton <zwwe@opti.cgi.net>
Cc: whitney@math.berkeley.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 Networking oddity
Date: Mon, 29 Jan 2001 10:51:30 -0800 [thread overview]
Message-ID: <3A75BBB2.63CE124C@napster.com> (raw)
In-Reply-To: <5.0.2.1.2.20010128140720.03465e38@209.54.94.12> <5.0.2.1.2.20010128140720.03465e38@209.54.94.12> <5.0.2.1.2.20010129002217.03362fe0@209.54.94.12>
Daniel Walton wrote:
>
> The server in question is running the tulip driver. dmesg reports:
>
> Linux Tulip driver version 0.9.13 (January 2, 2001)
>
> I have seen this same behavior on a couple of my servers running 3com
> 3c905c adaptors as well.
>
> The last time I was experiencing it I rebooted the system and it didn't
> solve the problem. When it came up it was still lagging. This would lead
> me to believe that it is caused by some sort of network condition, but what
> I don't know.
>
> If anyone has ideas, I'd be more than happy to run tests/provide more info..
>
If you are running an intelligent switch, double check to make sure your
duplex and speed match what the switch sees on it's port. The biggest
problem I've had with any of my machines is autonegotiation of port
speed and duplex. Typically all that is required is that I force speed
and duplex on the Linux end.
Jordan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101290314.f0T3E0601647@adsl-209-76-109-63.dsl.snfc21.pa cbell.net>
2001-01-29 5:57 ` 2.4.0 Networking oddity Daniel Walton
2001-01-29 3:14 ` Wayne Whitney
2001-01-29 6:27 ` Daniel Walton
2001-01-29 18:51 ` Jordan Mendelson [this message]
2001-02-05 18:15 ` 2.4.x latency Daniel Walton
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=3A75BBB2.63CE124C@napster.com \
--to=jordy@napster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@math.berkeley.edu \
--cc=zwwe@opti.cgi.net \
/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