Date: Wed, 11 Jul 2007 13:51:04 -0500 From: Josh Paetzel <josh@tcbug.org> To: freebsd-net@freebsd.org Cc: Paul Schmehl <pauls@utdallas.edu> Subject: Re: Question about bce driver Message-ID: <200707111351.07733.josh@tcbug.org> In-Reply-To: <0C1E29F62151D7884CFE26A2@utd59514.utdallas.edu> References: <BDD239C660ED0435A14C5A76@utd59514.utdallas.edu> <200707111230.24975.josh@tcbug.org> <0C1E29F62151D7884CFE26A2@utd59514.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3054455.kzUs4E71mx Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 11 July 2007, Paul Schmehl wrote: > > > > 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 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 that issue. Switching to the Intel card > would be a bit of a PITA on a remote, rack-mount server. :-( I was running the driver from STABLE until about March and it would=20 bounce the link up and down a couple times a day even under=20 relatively moderate load. (50-60 mbps) So perhaps there have been=20 improvements since then, but I gave up dealing with it. The driver=20 was utterly broken in 6.1-R (0.9.5), by the time 6.2-R was getting=20 rolled the driver in STABLE would at least not tip over under TCP=20 load, but it was trivial to wedge it with even moderate amounts of=20 UDP. I eventually reached the conclusion (correct or not) that you can't=20 fix crap hardware with a driver. =2D-=20 Thanks, Josh Paetzel --nextPart3054455.kzUs4E71mx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGlSabJvkB8SevrssRAmt3AJ9ed1RInFRe5j8CmVc4OF0abA/MugCdGQbQ VDSykirW/n2BmdD4x16ReUQ= =Sd8c -----END PGP SIGNATURE----- --nextPart3054455.kzUs4E71mx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707111351.07733.josh>