[tulip] Parity error on 2nd Tulip card
Abe Ward Kabakoff
Fri Feb 7 12:41:02 2003
After looking through the logs to find this info, it looks like the card
was always broken, even when it was the only tulip on the system. Could
this be a hardware problem?
>What driver version?
>What is the detection message?
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
PCI: Enabling device 00:06.0 (0014 -> 0017)
eth0: ADMtek Comet rev 17 at 0xc2839c00, 00:04:5A:4A:CD:77, IRQ 9.
PCI: Enabling device 00:0e.0 (0014 -> 0017)
eth1: ADMtek Comet rev 17 at 0xc283d800, 00:04:5A:6E:CF:59, IRQ 10.
Is that what you're looking for?
>>internal network (hooked up to a 10baseT hub) the driver prints out a
>>message that a system error occured (error number 0).
>What is the error message, including error numbers?
Jan 17 08:56:36 linux kernel: eth1: (6905) System Error occured (0)
This repeats ad nauseum with the 6905 ascending sequentially
>>I looked this up in
>>the code, and it is a parity error. I then promptly commented out that
>>part of the code so I wouldn't fill my logs. Oddly enough inspite of
>>these errors the masqing seems to work fine, although I think there is an
>>inordinate number of network collisions. Here is some basic info: (eth1
>>is the misbehaving card)
>>Output from tulip-diag (no options):
>>tulip-diag.c:v2.16 12/17/2002 Donald Becker (email@example.com)
>>Index #2: Found a ADMtek AL985 Centaur-P adapter at 0xf400.
>> Comet duplex is reported in the MII status registers.
>> Transmit started, Receive started.
>> The Rx process state is 'Waiting for packets'.
>> The Tx process state is 'Idle'.
>> The transmit threshold is 128.
>> Comet MAC address registers 6e5a0400 ffff59cf
>> Comet multicast filter 8000000840000000.
>>eth1 Link encap:Ethernet HWaddr 00:04:5A:6E:CF:59
>> RX packets:3808455 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:3934296 dropped:0 overruns:0 carrier:7657130
>> collisions:0 txqueuelen:100
>Yup, this is broken.