From owner-freebsd-net@FreeBSD.ORG  Thu Oct 29 18:12:34 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 2EEE21065670
	for <net@freebsd.org>; Thu, 29 Oct 2009 18:12:34 +0000 (UTC)
	(envelope-from davidch@broadcom.com)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19])
	by mx1.freebsd.org (Postfix) with ESMTP id 095628FC15
	for <net@freebsd.org>; Thu, 29 Oct 2009 18:12:33 +0000 (UTC)
Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.3.2)); Thu, 29 Oct 2009 11:05:39 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
	IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Thu, 29
	Oct 2009 11:07:01 -0700
From: "David Christensen" <davidch@broadcom.com>
To: "Tom Judge" <tom@tomjudge.com>
Date: Thu, 29 Oct 2009 11:05:37 -0700
Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver
Thread-Index: AcpYvZUvlI/Ka8HMQzO8nD0QpoRfTwABCT2A
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com>
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>
In-Reply-To: <4AE9D10F.4040703@tomjudge.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 66F706F93A01040636-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "rwilliams@borderware.com" <rwilliams@borderware.com>,
	Gideon Naim <gideon.naim@broadcom.com>, "net@freebsd.org" <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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2009 18:12:34 -0000

> > After fighting with the update process for a bit and then learning=20
> > about the live cycle manager I have managed to test the=20
> R610 with the=20
> > 5.0.9 firmware.
> >=20
> > On the face of it, it seems that this resolves the issue.
> >
> After a reboot this morning the error has resurfaced and the=20
> 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=20
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.

Dave=