From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 15:03:11 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 A2CEA16A403 for ; Thu, 12 Oct 2006 15:03:11 +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 10AAC43D46 for ; Thu, 12 Oct 2006 15:03:10 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k9CF334v065592; Thu, 12 Oct 2006 10:03:03 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <452E5928.2080500@centtech.com> Date: Thu, 12 Oct 2006 10:03:04 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Scott Long References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> <452D1A07.4070500@centtech.com> <20061012093714.GL59833@FreeBSD.org> <452E2E85.1040006@centtech.com> <452E3D96.5080402@samsco.org> In-Reply-To: <452E3D96.5080402@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; 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: stable@FreeBSD.org, davidch@broadcom.com, Bill Moran , netops@collaborativefusion.com, Gleb Smirnoff , kris@obsecurity.org Subject: Re: bce issues still outstanding X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com 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 15:03:11 -0000 There is no line for EISA in the GENERIC config file, nor can I find it in device.hints. The markings on the chip say it is a BCM5754, but it's being recognized as BCM5787. I currently have the machine at the db> prompt if someone can walk me through getting valuable information. ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com Scott Long wrote the following on 10/12/06 08:05: > Yeah, the error is probably a PCI error coming from the chipset, > not a RAM error. Unfortunately, there are a lot of mystery reasons > why a PCI error might get triggered, and the message isn't enough > to say what exactly it is. However, one simple test you can to > is to disable the EISA device in the kernel if you still have it in > there. > > Scott > > > Kevin Kramer wrote: >> 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? >>> >>