From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 16:54:49 2006 Return-Path: X-Original-To: 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 D18DA16A403; Thu, 12 Oct 2006 16:54:49 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from bbbx3.usdmm.com (relay1.us.mintel.com [63.174.175.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id B392243D5F; Thu, 12 Oct 2006 16:54:42 +0000 (GMT) (envelope-from tom@tomjudge.com) Received: from [0.0.0.0] (unknown [10.0.0.37]) by bbbx3.usdmm.com (Postfix) with ESMTP id BD6D45C5B; Thu, 12 Oct 2006 11:54:19 -0500 (CDT) Message-ID: <452E7129.2000105@tomjudge.com> Date: Thu, 12 Oct 2006 17:45:29 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: Scott Long References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> In-Reply-To: <452D0986.3020902@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, davidch@broadcom.com, Bill Moran , netops@collaborativefusion.com, glebius@freebsd.org, kris@obsecurity.org Subject: Re: bce issues still outstanding 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: Thu, 12 Oct 2006 16:54:49 -0000 Scott Long wrote: > Bill Moran wrote: >> I've copied many of the people who I've been working with directly on >> this issue. >> >> Can anyone provide a status update on these problems? Discussion seems >> to have stopped since Oct 5. >> >> Any new patches to test? >> > > I'm actively working on fixing the driver right now. > > Scott > If there are any patches you want testing I have 3 very expensive paperweights sat around the office at the moment in the form of Dell PE2950's with twin adapters in them: bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: on bce0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce0: Ethernet address: 00:13:72:60:35:8a bce1: mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus1: on bce1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce1: Ethernet address: 00:13:72:60:35:88 The easiest way to cause the watchdog time out on these systems is to write a file larger than 50Mb to an NFS file system that is mounted over UDP (TCP doesn't cause the time out strangely). From the testing I have done the timeout is triggered when arround 49Mb has been copied to the NFS server. Perhaps this could suggest a bug in the udp packet checksum offload code? I have 2 systems available to test on right now, one running code from RELENG_6 just after beta2 was announced, and one cvsup'd from the uk mirror today. The kernels are compiled with: option INVARIANTS option INVARIANT_SUPPORT However this doesn't cause a kernel panic. Let me know if you need any more information. Tom