Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Feb 2007 14:50:49 -0800
From:      Jeremy Chadwick <koitsu@FreeBSD.org>
To:        Greg Barniskis <nalists@scls.lib.wi.us>
Cc:        Vivek Khera <vivek@khera.org>, FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: Intermittent network issues with Freebsd 6.2
Message-ID:  <20070228225049.GA64944@icarus.home.lan>
In-Reply-To: <45E5FA49.8050509@scls.lib.wi.us>
References:  <20070215043533.GA3293@icarus.home.lan> <000b01c750bd$5a2d55b0$d801a8c0@dimuthu> <20070228092000.GA51292@icarus.home.lan> <200702281832.l1SIW2DF077797@lava.sentex.ca> <E7980669-771B-4DA7-9F90-3F2762C1BF59@khera.org> <45E5FA49.8050509@scls.lib.wi.us>

next in thread | previous in thread | raw e-mail | index | archive | help
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 |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070228225049.GA64944>