Date: Thu, 12 Oct 2006 07:05:26 -0600 From: Scott Long <scottl@samsco.org> To: Kevin Kramer <kramer@centtech.com> Cc: stable@FreeBSD.org, davidch@broadcom.com, Bill Moran <wmoran@collaborativefusion.com>, netops@collaborativefusion.com, Gleb Smirnoff <glebius@FreeBSD.org>, kris@obsecurity.org Subject: Re: bce issues still outstanding Message-ID: <452E3D96.5080402@samsco.org> In-Reply-To: <452E2E85.1040006@centtech.com> References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> <452D1A07.4070500@centtech.com> <20061012093714.GL59833@FreeBSD.org> <452E2E85.1040006@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452E3D96.5080402>