From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 20:06:07 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18E71106568F for ; Thu, 29 Oct 2009 20:06:07 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id C81D58FC26 for ; Thu, 29 Oct 2009 20:06:06 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id BE4BF48A7F; Thu, 29 Oct 2009 20:06:05 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCRPn6tnQmZf; Thu, 29 Oct 2009 20:06:02 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id C68E848A7D; Thu, 29 Oct 2009 20:06:01 +0000 (GMT) Message-ID: <4AE9F576.4060101@tomjudge.com> Date: Thu, 29 Oct 2009 20:05:10 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 20:06:07 -0000 David Christensen wrote: >>> After fighting with the update process for a bit and then learning >>> about the live cycle manager I have managed to test the >> R610 with the >>> 5.0.9 firmware. >>> >>> On the face of it, it seems that this resolves the issue. >>> >> After a reboot this morning the error has resurfaced and the >> box is again useless. > > Can you try a different test? Power-on the system with the network > cable attached to an idle switch (i.e. keep all network traffic from > being forwarded to the NIC during driver initialization). Does the > system power up successfully? Repeatedly? The problem I saw > was caused by network traffic being handled by the NIC during driver > initialization. If you still see the same behavior then this might > be a different issue. > Looks like we are heading in the right direction here. Setup: R610[bce1]->Netgear 100/10 unmanaged switch-[uplink]->Managed server access switch. The R610 is the only thing connected to the netgear switch. When the uplink was severed during boot up it was reconnected after the link up event and while the NFS mounts where being mounted. Cold reboots are with the server shutdown with the psu's remaining connected and then restarted. Warm are just 'shutdown -r now' Ice are from the psus disconnected from the mains supply. These results are time ordered. Type Uplink Result Warm No Works Warm No Works Warm No Works Cold No Works Warm No Works Cold No Works Warm No Works Ice No Works Warn No Works Ice Yes Works Warm Yes Works Cold Yes Works Warm Yes Works Ice Bybass Works Warm Bypass Fails Cold Bypass Works - paniced on shutdown spin lock (sched) held to long pid 0 Cold Bypass Works Warm Bypass Fails We can provide full remote access to the following hardware (via enterprise drac) if required and on site hands if this will help get this issue resolved. 3 * R610 4 * R410 7 * R710 Tom