From owner-freebsd-current@FreeBSD.ORG Sat Nov 15 18:43:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F4B216A4CE for ; Sat, 15 Nov 2003 18:43:38 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CFFE43FBF for ; Sat, 15 Nov 2003 18:43:37 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])hAG2hRJD027063; Sun, 16 Nov 2003 13:43:27 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.9p1/8.12.9/Submit) id hAG2hQ7v027062; Sun, 16 Nov 2003 13:43:26 +1100 (EST) (envelope-from peter) Date: Sun, 16 Nov 2003 13:43:26 +1100 From: Peter Jeremy To: Ceri Davies , freebsd-current@freebsd.org Message-ID: <20031116024326.GC74756@server.vk2pj.dyndns.org> References: <20031115164720.I13393@hewey.af.speednet.com.au> <20031115071458.GA29973@lizzy.catnook.com> <20031115202744.GG60410@submonkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031115202744.GG60410@submonkey.net> User-Agent: Mutt/1.4.1i Subject: Re: dc still reporting collisions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 02:43:38 -0000 On Sat, Nov 15, 2003 at 08:27:44PM +0000, Ceri Davies wrote: These >probably are actual collisions though. The OP's point is that >collisions are supposed to be impossible on a full duplex link, >whereas in your situation they aren't. The collision mechanism is used for flow control on full-duplex links. A very high collision rate would normally indicate a half/full duplex mismatch. A low collision rate would normally indicate that the switch can't handle the load and is throttling back your system. (Other options are broken NICs and/or cables). Peter