From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 12:00:37 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 A5B4716A40F for ; Thu, 12 Oct 2006 12:00:37 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF1A43D81 for ; Thu, 12 Oct 2006 12:00:32 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [127.0.0.1] ([192.168.45.151]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k9CC0NGU035802; Thu, 12 Oct 2006 07:00:26 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <452E2E85.1040006@centtech.com> Date: Thu, 12 Oct 2006 07:01:09 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Gleb Smirnoff References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> <452D1A07.4070500@centtech.com> <20061012093714.GL59833@FreeBSD.org> In-Reply-To: <20061012093714.GL59833@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/2026/Thu Oct 12 01:47:06 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: davidch@broadcom.com, Bill Moran , stable@FreeBSD.org, netops@collaborativefusion.com, 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 12:00:37 -0000 I'll try that, but we received a response from David C. and few weeks ago (on another thread) that the BCE driver should be picking up this NIC. The latest 6.1 stable does not panic with the NIC disabled in the BIOS. Gleb Smirnoff wrote: > Kevin, > > On Wed, Oct 11, 2006 at 11:21:27AM -0500, Kevin Kramer wrote: > K> here is a picture of a panic i get on a Dell Precision 390 booting > K> 6.2-beta2_amd64. hope this helps. > K> > K> http://users.centtech.com/~kramer/broadcom/bge_prec390.jpg > > Well, although the message above is about bge(4) identified, the > panic says that the CPU received NMI due to RAM parity error. > > Have you tried replacing the RAM? > -- Kevin Kramer Sr. Systems Administrator Centaur Technology, Inc. 512.418.5725