From owner-freebsd-net@FreeBSD.ORG Wed Nov 18 02:28:54 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 C0E6C106566C for ; Wed, 18 Nov 2009 02:28:54 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.freebsd.org (Postfix) with ESMTP id 909FC8FC16 for ; Wed, 18 Nov 2009 02:28:54 +0000 (UTC) Received: from [10.9.200.133] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 17 Nov 2009 18:28:03 -0800 X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Tue, 17 Nov 2009 18:29:25 -0800 From: "David Christensen" To: "Tom Judge" Date: Tue, 17 Nov 2009 18:28:02 -0800 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: Acpj5CTKoda469hiR0y11mST9rIP4wEEk7jA Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A20E0E802@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> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA0B11.2050209@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA1183.7050306@tomjudge.com> <4AEB2571.7090006@tomjudge.com> <4AFAE428.5090907@quip.cz> <5D267A3F22FD854F8F48B3D2B52381933A20D4C55D@IRVEXCHCCR01.corp.ad.broadcom.com> <4AFAF542.8050004@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A20D4CA70@IRVEXCHCCR01.corp.ad.broadcom.com> <4AFC862B.6060805@tomjudge.com> In-Reply-To: <4AFC862B.6060805@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: 671D843938O10896552-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "net@freebsd.org" , "rwilliams@borderware.com" , Miroslav Lachman <000.fbsd@quip.cz>, Gideon Naim 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: Wed, 18 Nov 2009 02:28:54 -0000 > > I haven't been able to reproduce it on the r710 I have in house. > > Checking with other groups now to see if they have one a I can use,=20 > > though I'm not sure why the system would make a difference for this=20 > > particular issue. Just wanted to confirm that you're using=20 > the driver=20 > > built into the kernel (as opposed to a module) and that a warm boot=20 > > means running the "reboot" or "shutdown -r" > > commands while a cold boot means pressing the front panel=20 > power button=20 > > or using the DRAC to power down the system. > >=20 > > Dave >=20 > Hi Dave, >=20 > Thanks for the update. >=20 > All these are true. >=20 > warm - shutdown -r now > cold - from the power button (iDRACs are not configured yet). >=20 > bce is compiled into the kernel (tested with GENERIC kernel=20 > from 8-RC2 as well as 7.1 with the 7.2 driver plus the split=20 > header patch). >=20 > For the record we also have not been able to reproduce the=20 > issue on the R710 only the R610. Still no luck on my r710, even after reverting to the production firmware and blasting broadcast traffic at the interface during reset. Let me check again on an r610. Dave=