From owner-freebsd-stable@FreeBSD.ORG Mon Jan 15 23:36:24 2007 Return-Path: X-Original-To: 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 2E40116A407 for ; Mon, 15 Jan 2007 23:36:24 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1252613C448 for ; Mon, 15 Jan 2007 23:36:24 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CF4691A4D91; Mon, 15 Jan 2007 15:36:23 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DCC5D516FA; Mon, 15 Jan 2007 18:36:20 -0500 (EST) Date: Mon, 15 Jan 2007 18:36:20 -0500 From: Kris Kennaway To: Sven Willenberger Message-ID: <20070115233620.GA53399@xor.obsecurity.org> References: <20061215192958.GA86926@xor.obsecurity.org> <20061215212040.GG23698@deviant.kiev.zoral.com.ua> <1166463200.11562.5.camel@lanshark.dmv.com> <4596F06D.30004@dmv.com> <20070113201106.GD66260@xor.obsecurity.org> <1168878813.13113.2.camel@lanshark.dmv.com> <20070115182227.GA30242@xor.obsecurity.org> <1168887808.13113.7.camel@lanshark.dmv.com> <20070115202456.GA31969@xor.obsecurity.org> <1168896623.13113.15.camel@lanshark.dmv.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <1168896623.13113.15.camel@lanshark.dmv.com> User-Agent: Mutt/1.4.2.2i Cc: Kostik Belousov , stable@freebsd.org, Kris Kennaway Subject: Re: bge panic (Re: Not panic in nfsd (Re: panic in nfsd on 6.2-RC1)) 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: Mon, 15 Jan 2007 23:36:24 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 15, 2007 at 04:30:23PM -0500, Sven Willenberger wrote: > On Mon, 2007-01-15 at 15:24 -0500, Kris Kennaway wrote: > > On Mon, Jan 15, 2007 at 02:03:28PM -0500, Sven Willenberger wrote: > > > On Mon, 2007-01-15 at 13:22 -0500, Kris Kennaway wrote: > > > > On Mon, Jan 15, 2007 at 11:33:33AM -0500, Sven Willenberger wrote: > > > >=20 > > > > > > This is indicating a problem either with your bge hardware or t= he driver. > > > > > >=20 > > > > > > Kris > > > > >=20 > > > > > I suspect the driver: This same hardware setup was being used as a > > > > > databse server with FreeBSD 5.4. I had been using the bge driver = but set > > > > > at base100T without any issue at all. It was when I did a clean i= nstall > > > > > of 6.2-Prerelease and setting bge to use the full gigE speed (via > > > > > autonegotiate) that these issues cropped up. > > > >=20 > > > > Be careful before you start blaming FreeBSD - since you did not test > > > > the failing hardware configuration in the older version of FreeBSD = you > > > > cannot yet determine that it is a driver regression. > > > >=20 > > > > Kris > > >=20 > > > I will freely admit that this may be circumstantial, that the hardware > > > failed at the same time I upgraded to the newer version of FreeBSD. It > > > could also be that there is an issue with the bge driver being used w= ith > > > 1000 (gigE) speeds instead of at fastE speeds as I used it with the 5= .4 > > > release (same hardware). > >=20 > > The latter is what I am referring to. Your hardware may never have > > worked in gige mode due to your hardware being broken (yes, this > > happens), or it could be a freebsd driver issue either introduced in > > 6.x or present in 5.4 too. You just haven't ruled these cases out. > >=20 > > Anyway, since you're happy with your present workaround we'll have to > > just drop the issue for now. > >=20 > > Kris >=20 > As the box in question is now fully production I can no longer "guinea > pig" it. However, I will attempt to set up a test bed with similar > hardware and try and push as much traffic through the bge interface at > gigE speeds as I can in an effort to duplicate this issue. If it does > crop up, this box should allow me to more effectively provide debugging > information as it will not be a production unit. Although the current > workaround is satisfactory for now (and to that extent I am "happy") I > would much rather have the available headroom of full gigE traffic to > this server so I would like to see if I can reproduce the error or at > least find out if it is a hardware issue (if nothing else than for my > own edification). OK, let us know how that goes. Kris --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFrA/0Wry0BWjoQKURAuQwAJ9woaWgucWYTNwA2wz3RtUSiLddfgCgrYqk 5VhPdPyBE8wbNMe27fQC/P0= =CcpV -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--