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?
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
