From owner-freebsd-stable@FreeBSD.ORG Wed Feb 28 22:51:11 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 31C4D16A404 for ; Wed, 28 Feb 2007 22:51:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.192.82]) by mx1.freebsd.org (Postfix) with ESMTP id 1AFCB13C4B3 for ; Wed, 28 Feb 2007 22:51:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (rwcrmhc12) with ESMTP id <20070228225110m1200j64iqe>; Wed, 28 Feb 2007 22:51:10 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BBFC71FA03D; Wed, 28 Feb 2007 14:50:49 -0800 (PST) Date: Wed, 28 Feb 2007 14:50:49 -0800 From: Jeremy Chadwick To: Greg Barniskis Message-ID: <20070228225049.GA64944@icarus.home.lan> Mail-Followup-To: Greg Barniskis , Vivek Khera , FreeBSD Stable References: <20070215043533.GA3293@icarus.home.lan> <000b01c750bd$5a2d55b0$d801a8c0@dimuthu> <20070228092000.GA51292@icarus.home.lan> <200702281832.l1SIW2DF077797@lava.sentex.ca> <45E5FA49.8050509@scls.lib.wi.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E5FA49.8050509@scls.lib.wi.us> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Vivek Khera , FreeBSD Stable Subject: Re: Intermittent network issues with Freebsd 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 22:51:11 -0000 On Wed, Feb 28, 2007 at 03:55:21PM -0600, Greg Barniskis wrote: > On our Dell PE2950 units, we had to do the same thing (disable and > replace the Broadcom interfaces), and that was running Windows > Server 2k3. The problem really seems to be flakiness of the chips or > firmware, not necessarily flakiness in the drivers for FreeBSD. > Maybe it's both, I don't know. > > My point is that Broadcom cards have had some serious problems on > other platforms too, and not just recently. Other NIC brands have > never given us nearly as much trouble. Sounds like I'm going to have to purchase a dual NIC card and install it in our server, then disable the onboard Broadcom NICs. Amusingly, I'll point out that on all newer Supermicro boards (Intel chipset-based), Supermicro is using Intel NICs and PHYs, and no longer Broadcom. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |