From owner-freebsd-stable@FreeBSD.ORG Fri Oct 6 21:14:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BFAD16A412 for ; Fri, 6 Oct 2006 21:14:41 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE98143D46 for ; Fri, 6 Oct 2006 21:14:40 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ideh6pjqlvyjmkcg@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k96LEd1Y019160 for ; Fri, 6 Oct 2006 14:14:39 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k96LEdqv019159 for freebsd-stable@freebsd.org; Fri, 6 Oct 2006 14:14:39 -0700 (PDT) (envelope-from jmg) Date: Fri, 6 Oct 2006 14:14:39 -0700 From: John-Mark Gurney To: freebsd-stable@freebsd.org Message-ID: <20061006211439.GB793@funkthat.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <4523764E.3070309@ant.uni-bremen.de> <45252483.5040708@ant.uni-bremen.de> <20061005160819.GA13417@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061005160819.GA13417@icarus.home.lan> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Subject: Re: NFS client slow on amd64 6.2-PRERELEASE #2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2006 21:14:41 -0000 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 down; ifconfig 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."