From owner-freebsd-net@FreeBSD.ORG Wed Jul 11 17:37:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F44816A468 for ; Wed, 11 Jul 2007 17:37:54 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 4028413C4BB for ; Wed, 11 Jul 2007 17:37:54 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id CFACF654FD for ; Wed, 11 Jul 2007 12:37:53 -0500 (CDT) Date: Wed, 11 Jul 2007 12:37:53 -0500 From: Paul Schmehl To: freebsd-net@freebsd.org Message-ID: <0C1E29F62151D7884CFE26A2@utd59514.utdallas.edu> In-Reply-To: <200707111230.24975.josh@tcbug.org> References: <4694940D.9050408@tomjudge.com> <200707111230.24975.josh@tcbug.org> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========863A1BABDF4141065CAD==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Question about bce driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 17:37:54 -0000 --==========863A1BABDF4141065CAD========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Wednesday, July 11, 2007 12:30:21 -0500 Josh Paetzel =20 wrote: > On Wednesday 11 July 2007, Tom Judge wrote: >> Paul Schmehl wrote: >> > I'm running 6.1 RELEASE (i386) and I've been replacing the >> > if_bce.c file with a slightly newer one that at least got the >> > driver working without hard lockups that required a reboot to >> > fix. (Rather problematic on a remotely located web server.) >> > >> > If I download the latest driver from cvs (1.33), should I also >> > replace the if_bcefw.h and if_bcereg.h files with the newer >> > versions? Will the NIC work without creating new problems? >> > Right now I get an occasional "flapping" of the NIC link state >> > (down, up , down, up, etc.) but it at least works most of the >> > time. I don't want to buildworld and get suprised by a >> > non-functioning NIC. :-) >> > >> > If I use the newer versions, will I also need to use some other >> > newer files that are called by them? Or would it be better to >> > upgrade the entire box to 6.2? >> > >> > FreeBSD www.stovebolt.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 >> > # 2: >> > >> > grep bce /var/run/dmesg.boot >> > bce0: mem >> > 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 >> > bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz >> > miibus0: on bce0 >> > bce0: Ethernet address: 00:13:72:fb:2a:ad >> > bce1: mem >> > 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 >> > bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz >> > miibus1: on bce1 >> > bce1: Ethernet address: 00:13:72:fb:2a:ab >> >> Hi Paul, >> >> From the testing that I have been doing for the last few months >> the driver in 6.2 is stable if you are not using jumbo frames and >> there is a light-moderate network load. >> >> However if you want to use Jumbo frames the driver is very >> unstable. I posted a patch against 6.2 which should fix some load >> based issues in the driver with standard frame sizes. >> >> Tom > > Paul, I was never able to solve the link up/link down problems with > the driver....I was using the drivers from STABLE for a while, and > without jumbo frames everything worked somewhat ok most of the > time....the ultimate solution was to just get the intel PCI-X card > and stop using the broadcoms. Ouch! So even updating to the latest driver doesn't solve the link state=20 issue? I don't use jumbo frames, but it's critical that this server remain = in service 24/7, so I don't want to upgrade if there's no improvement in=20 that issue. Switching to the Intel card would be a bit of a PITA on a=20 remote, rack-mount server. :-( --=20 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========863A1BABDF4141065CAD==========--