bce issues still outstanding

[Kevin Kramer]

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?
>>>
>>