From owner-freebsd-stable@FreeBSD.ORG Mon Jan 15 21:23:27 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 CA1F216A412 for ; Mon, 15 Jan 2007 21:23:27 +0000 (UTC) (envelope-from sven@dmv.com) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.freebsd.org (Postfix) with ESMTP id 86BE613C45B for ; Mon, 15 Jan 2007 21:23:27 +0000 (UTC) (envelope-from sven@dmv.com) Received: from mail-gw-cl-b.dmv.com (mail-gw-cl-b.dmv.com [216.240.97.39]) by smtp-gw-cl-d.dmv.com (8.12.10/8.12.10) with ESMTP id l0FLNPJX059962; Mon, 15 Jan 2007 16:23:25 -0500 (EST) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by mail-gw-cl-b.dmv.com (8.12.9/8.12.9) with ESMTP id l0FLNP8s006935; Mon, 15 Jan 2007 16:23:25 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: Kris Kennaway In-Reply-To: <20070115202456.GA31969@xor.obsecurity.org> References: <20061215181548.GA58555@xor.obsecurity.org> <1166209936.6317.21.camel@lanshark.dmv.com> <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> Content-Type: text/plain Date: Mon, 15 Jan 2007 16:30:23 -0500 Message-Id: <1168896623.13113.15.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.39 Cc: Kostik Belousov , stable@freebsd.org 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 21:23:27 -0000 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: > > > > > > > > This is indicating a problem either with your bge hardware or the driver. > > > > > > > > > > Kris > > > > > > > > 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 install > > > > of 6.2-Prerelease and setting bge to use the full gigE speed (via > > > > autonegotiate) that these issues cropped up. > > > > > > 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. > > > > > > Kris > > > > 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 with > > 1000 (gigE) speeds instead of at fastE speeds as I used it with the 5.4 > > release (same hardware). > > 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. > > Anyway, since you're happy with your present workaround we'll have to > just drop the issue for now. > > Kris 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). Sven