From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 13:06:10 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 9DBB816A4CA; Thu, 12 Oct 2006 13:06:10 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0939C43D6A; Thu, 12 Oct 2006 13:05:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9CD5Taj070236; Thu, 12 Oct 2006 07:05:36 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <452E3D96.5080402@samsco.org> Date: Thu, 12 Oct 2006 07:05:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Kevin Kramer References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> <452D1A07.4070500@centtech.com> <20061012093714.GL59833@FreeBSD.org> <452E2E85.1040006@centtech.com> In-Reply-To: <452E2E85.1040006@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org 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 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 13:06:10 -0000 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? >> >