From owner-freebsd-stable@FreeBSD.ORG Wed Oct 18 22:01:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4933916A416 for ; Wed, 18 Oct 2006 22:01:39 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C57CB43D78 for ; Wed, 18 Oct 2006 22:01:34 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9IM1Q8Q017560; Wed, 18 Oct 2006 16:01:32 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4536A430.4070807@samsco.org> Date: Wed, 18 Oct 2006 16:01:20 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Judge References: <45364782.8090209@samsco.org> <45366122.6090704@mintel.com> <20061018175257.GA97258@xor.obsecurity.org> <45367B71.40704@tomjudge.com> In-Reply-To: <45367B71.40704@tomjudge.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: Jason Thomson , freebsd-stable@freebsd.org, Conrad Burger , Kris Kennaway Subject: Re: When will the new BCE driver in HEAD be incorporated into RELENG_6? 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, 18 Oct 2006 22:01:39 -0000 Tom Judge wrote: > Kris Kennaway wrote: > >> On Wed, Oct 18, 2006 at 06:15:14PM +0100, Jason Thomson wrote: >> >> >>> Using the driver from HEAD* in the latest RELENG_6 didn't fix our >>> problems. >>> >>> We could still trigger the Watchdog timeout when copying a local file to >>> an NFS mounted filesystem (UDP mount, GigE speeds). >>> >>> It was also possible to trigger this bug with multiple simultaneous TCP >>> streams, but that took a little longer. >>> >>> Copying a local file to an NFS/UDP filesystem would trigger the bug in a >>> few seconds. >>> >>> If there's anything we can do to help debug this, please let us know. >>> >> >> >> Per my previous mails, the (known) bce watchdogs are symptoms of >> driver bugs which can be usefully converted into panics by enabling >> INVARIANTS and INVARIANT_SUPPORT. Please do so, then report what >> happens. >> >> Kris >> > > Hi Kris, > > I am a colleague of Jason's, when we were testing this patch the kernel > used had both options set: > > option INVARIANTS > option INVARIANT_SUPPORT > > Although on several boxes we have failed to cause a kernel panic, only > watchdog timeouts. However the last crash that we reproduced did > trigger several: > > bce: need to defrag > > Messages on the console before the watchdob timeout occured. > > > Tom This is a debugging message that I accidentally left in. It may relate to the problem, I'll take a look. Scott