eth0 system error

Examination of /var/log/messages shows thousands of messages of the form:

smoothwall kernel: eth0 (423941) System error occured

(spelling of 'occured' is intended)

I've scoured NG and the web and can find no reference to this message.
I changed the network card in eth0 to no avail

Does anyone have a suggestion?
The PC is Smoothwall Express2 firewall/router


John Stolz

Jeroen Geilman <(E-Mail Removed)> wrote:

> Try another slot - a BM capable one, for preference.

BM???

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

John Stolz wrote:

> Examination of /var/log/messages shows thousands of messages of the form:
>
> smoothwall kernel: eth0 (423941) System error occured
>
> (spelling of 'occured' is intended)
>
> I've scoured NG and the web and can find no reference to this message.

Hmm.. Googling for "eth0 system error" hits me 62000 times.

> I changed the network card in eth0 to no avail
>
> Does anyone have a suggestion?

I grepped the kernel source - it's in the tulip driver.

(/usr/src/linux/drivers/net/tulip/interrupt.c to be precise.)

The error is a PCI parity error - meaning either the MoBo and NIC don't
like each other, or the PCI slot is flaky.

Try another slot - a BM capable one, for preference.

--
Jeroen Geilman

Analog bits courtesy of adaptr.

Thanks for responding.
On Thu, 27 May 2004 01:41:51 +0200, Jeroen Geilman wrote:

> John Stolz wrote:
>
>> Examination of /var/log/messages shows thousands of messages of the form:
>>
>> smoothwall kernel: eth0 (423941) System error occured
>>
>> (spelling of 'occured' is intended)
>>
>> I've scoured NG and the web and can find no reference to this message.
>
> Hmm.. Googling for "eth0 system error" hits me 62000 times.
yes, but none of them seems useful - if you use the (in)correct spelling
in the error message and/or include kernel then you get close to zip.


>
>> I changed the network card in eth0 to no avail
>>
>> Does anyone have a suggestion?
>
> I grepped the kernel source - it's in the tulip driver.
>
> (/usr/src/linux/drivers/net/tulip/interrupt.c to be precise.)
>
> The error is a PCI parity error - meaning either the MoBo and NIC don't
> like each other, or the PCI slot is flaky.
>
> Try another slot - a BM capable one, for preference.

I think I fixed it - the machine has two eth cards, i've tried various
combinations of cards and slots and some of them work in some combinations
and others don't. For eg a Netgear FA311 in one slot and an SMC
in the other won't work - swap them around and they work fine. A tulip
and a FA311 won't work in any combination.

I've tried lots of combinations, most don't work, but some do. don't ask
me why.