From: Lee Revell <rlrevell@joe-job.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-os@analogic.com, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Network speed Linux-2.6.10
Date: Tue, 01 Mar 2005 15:35:31 -0500 [thread overview]
Message-ID: <1109709331.17405.2.camel@mindpipe> (raw)
In-Reply-To: <4224D0F5.4050400@candelatech.com>
On Tue, 2005-03-01 at 12:30 -0800, Ben Greear wrote:
> Lee Revell wrote:
> > On Tue, 2005-03-01 at 12:20 -0800, Ben Greear wrote:
> >
> >>What happens if you just don't muck with the NIC and let it auto-negotiate
> >>on it's own?
> >
> >
> > This can be asking for trouble too (auto negotiation is often buggy).
> > What if you hard set them both to 100/full?
>
> I have not noticed any buggy autonegotiation with the e100 driver in several
> years...
>
Sorry, I misread the post. He tried this.
I was under the impression this was due to inconsistent implementation
of autonegotiation in hardware. When I was an ISP sysadmin we had this
problem with various devices (Cisco switches, Linux and BSD/OS
machines). A device would get power cycled and one side would come up
100/full, the other 100/half. We ended up hard setting everything.
Lee
next prev parent reply other threads:[~2005-03-01 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 19:29 Network speed Linux-2.6.10 linux-os
2005-03-01 20:20 ` Ben Greear
2005-03-01 20:24 ` Lee Revell
2005-03-01 20:27 ` linux-os
2005-03-01 20:30 ` Miquel van Smoorenburg
2005-03-01 20:36 ` Lee Revell
2005-03-01 20:30 ` Ben Greear
2005-03-01 20:35 ` Lee Revell [this message]
2005-03-02 16:16 ` venom
2005-03-02 16:14 ` venom
2005-03-02 17:40 ` Horst von Brand
2005-03-02 17:48 ` linux-os
2005-03-01 20:26 ` linux-os
2005-03-01 20:34 ` Ben Greear
2005-03-02 0:51 ` Paul Dickson
2005-03-02 1:02 ` Baruch Even
2005-03-02 3:24 ` Paul Dickson
2005-03-02 9:37 ` Baruch Even
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=1109709331.17405.2.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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