From owner-freebsd-net@FreeBSD.ORG Thu Nov 12 21:34:12 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 57E091065670 for ; Thu, 12 Nov 2009 21:34:12 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by mx1.freebsd.org (Postfix) with ESMTP id 29BEB8FC1A for ; Thu, 12 Nov 2009 21:34:11 +0000 (UTC) Received: from [10.9.200.133] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 12 Nov 2009 13:33:57 -0800 X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Thu, 12 Nov 2009 13:35:18 -0800 From: "David Christensen" To: "Tom Judge" Date: Thu, 12 Nov 2009 13:33:55 -0800 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: Acpi9TDWvOp4UN/YRJ+kXhJ420Zn4AA6hNKA Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A20D4CA70@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> In-Reply-To: <4AFAF542.8050004@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: 66E2A0CF3C86344740-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: Thu, 12 Nov 2009 21:34:12 -0000 > Is there any progress on this issue? We can provide access=20 > to hardware with this fault (Specifically the R610). 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, though I'm not sure why the system would make a difference=20 for this particular issue. Just wanted to confirm that you're=20 using the driver built into the kernel (as opposed to a module) and that a warm boot means running the "reboot" or "shutdown -r" commands while a cold boot means pressing the front panel power button or using the DRAC to power down the system. Dave=