From owner-freebsd-stable@FreeBSD.ORG Wed Nov 29 17:34:37 2006 Return-Path: X-Original-To: freebsd-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 233E016A4FF for ; Wed, 29 Nov 2006 17:34:37 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16D4643CB4 for ; Wed, 29 Nov 2006 17:34:25 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (sccrmhc14) with ESMTP id <20061129173416014006h36de>; Wed, 29 Nov 2006 17:34:17 +0000 From: Josh Paetzel To: freebsd-stable@freebsd.org Date: Wed, 29 Nov 2006 11:33:56 -0600 User-Agent: KMail/1.9.4 References: <200611290640.47326.josh@tcbug.org> <456DB8AC.8010508@samsco.org> In-Reply-To: <456DB8AC.8010508@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611291133.56821.josh@tcbug.org> Cc: Subject: Re: Dell PE 1950 bce NICs revisited 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: Wed, 29 Nov 2006 17:34:37 -0000 On Wednesday 29 November 2006 10:43, Scott Long wrote: > Josh Paetzel wrote: > > I've been using 6.1-R on a PE1950 for some time now. The stock > > bce driver doesn't work at all. I dug up a driver off the web > > (0.9.6) that worked fine with my workload (basically all TCP) but > > in talking to Scott I discovered that UDP traffic was a problem > > for this driver. Some time ago I upgraded to the driver in > > -STABLE. This driver also appears to work fine, but about once a > > day I get the following: > > > > Nov 29 01:16:47 server2 kernel: > > bce1: /usr/src/sys/dev/bce/if_bce.c(5000): Watch > > dog timeout occurred, resetting! > > Nov 29 01:16:47 server2 kernel: bce1: link state changed to DOWN > > Nov 29 01:16:48 server2 kernel: bce1: link state changed to UP > > > > Pretty minor complaint, as it doesn't really affect the operation > > of the box, but I suppose it's a sign that there's still some > > work to be done. > > > > $FreeBSD: src/sys/dev/bce/if_bce.c,v 1.2.2.6 2006/10/24 > > > > As I write this I see there has been some further work on the > > driver, so I think I'll upgrade it and see what happens. > > It's possible that rev 1.2.2.6 will fix what you're seeing. If > not, then it might be the general issue with the watchdog framework > being unreliable that we addressed with the em driver. If so, then > it's mostly harmless. > > Scott > The string I pasted is what I was using. Rebuilt using: /repoman/r/ncvs/src/sys/dev/bce/if_bce.c,v 1.2.2.6.2.1 this morning. I'll give it a few days and see how it's working. I think either way it's harmless. It happens about once a day, and strangely enough it's almost always in periods of very low load. -- Thanks, Josh Paetzel