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