From owner-freebsd-hackers Wed May 15 3:11: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from marvin.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id CDD0137B408; Wed, 15 May 2002 03:10:52 -0700 (PDT) Received: (from root@localhost) by marvin.trident-uk.co.uk (8.11.1/8.11.1) id g4F9sNw30183; Wed, 15 May 2002 10:54:23 +0100 (BST) Received: from trident-uk.co.uk (root@mufuf.trident-uk.co.uk [194.207.93.63]) by marvin.trident-uk.co.uk (8.11.1/8.11.1av) with ESMTP id g4F9sMN30174; Wed, 15 May 2002 10:54:22 +0100 (BST) Received: (from jamie@localhost) by trident-uk.co.uk (8.11.6/8.11.6) id g4FAKC407416; Wed, 15 May 2002 11:20:12 +0100 (BST) (envelope-from jamie) Date: Wed, 15 May 2002 11:20:12 +0100 From: Jamie Heckford To: Matthew Dillon Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NFS Problems with Quantum Snapserver 4100 (BGE Cards!) Message-ID: <20020515112012.A7390@mufuf.trident-uk.co.uk> Reply-To: jamie@tridentmicrosystems.co.uk References: <20020513181756.A53366@mufuf.trident-uk.co.uk> <200205131808.g4DI8JnE069036@apollo.backplane.com> <20020514102221.A55183@mufuf.trident-uk.co.uk> <200205141853.g4EIrxN8075305@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200205141853.g4EIrxN8075305@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, May 14, 2002 at 11:53:59AM -0700 X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Already running the card and switch port in 100BaseTX FDX (forced) :) Would use GigE if the switch supported it tho.... Thus spake Matthew Dillon (dillon@apollo.backplane.com) : > It should also work if you force the GigE card into 100BaseTX mode, > assuming the switch can deal with it. Though of course then you are > not getting GigE speeds. > > Your description is very similar to a problem I had on my 2550's that > Bill Paul finally solved. It turned out that my 2550's (BCM5700) were > not initializing the polynomial functions properly and this resulted > in packet loss. Whenever you get bit stuffing packet loss like that, > certain bit patterns will *always* fail. But I'm sure this issue has > already been dealt with on the 5701 so the problem you are having is > probably different. > > The result is the appearance of hicups and delays on a TCP connection, > and repeatable hangs when just the wrong data pattern is transmitted > (because that packet winds up failing every time rather then just some > of the time). > > Another possibility in regards to packet loss is simply a bad cable > (if you are running GigE over copper). GigE is very sensitive to cable > issues and a bad crimp will screw things up easily. > > In anycase, my feeling about GigE in general is that it's a great cheap > way to aggregate data on an uplink, or to an NFS server that needs it, > but the incremental cost and hassle factor are still too high to > extend the benefit to generic servers. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message