Date: Fri, 6 Oct 2006 14:14:39 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: freebsd-stable@freebsd.org Subject: Re: NFS client slow on amd64 6.2-PRERELEASE #2 Message-ID: <20061006211439.GB793@funkthat.com> In-Reply-To: <20061005160819.GA13417@icarus.home.lan> References: <4523764E.3070309@ant.uni-bremen.de> <45252483.5040708@ant.uni-bremen.de> <20061005160819.GA13417@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote this message on Thu, Oct 05, 2006 at 09:08 -0700:
> The problem in that case turned out to be duplex-related. Both
> boxes were auto-negotiating with the Cisco switch correctly, and
> indeed the Cisco labelled them as auto-100/full, but as anyone who
> is familiar with Ciscos knows, auto-negotiation on Catalysts is
> far from reliable. Both boxes reported auto-neg and being at 100/full
> as well. I ended up hard-setting the boxes to use 100/full, and
> set the switch ports to 100/full, then rebooted both boxes (yes,
> this is sometimes required, as driver auto-neg code is a bit tweaky);
> voila, problem fixed.
It appears that some ethernet drivers don't reset the phy (bring the
link down) when changing media (duplex setting, etc).. This means that
if you boot w/ autoselect, and the switch autoselects to 100/full, but
then later change it to 100/full (w/ autoselect off) it will work fine..
but then if the cabel is pulled, or the switch resets, it attempts to
reautoselect, but falls back to 100/half while you are still running
100/full...
As you can imagine, it causes a very hard to track down problem since
the time it breaks is not readily apparent...
an ifconfig <iface> down; ifconfig <iface> up may help resolve this
issue if you are not sure...
I have just committed a patch to fxp0 to do this...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061006211439.GB793>