[tulip] Parity error on 2nd Tulip card

[Abe Ward Kabakoff]

Hello All,

I am having problems with one of my two tulip cards (ADMtek AL985
Centaur-P both of them) in an IP-masqing machine.  It is running kernel
2.4.20 and SuSE 7.2. On almost every packet on the connection to the
internal network (hooked up to a 10baseT hub) the driver prints out a
message that a system error occured (error number 0).  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 (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xf800.
 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 4a5a0400 ffff77cd
  Comet multicast filter 8000000040040000.
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.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.

- - - - - - - - - - - - -

ifconfig eth0; ifconfig eth1
eth0      Link encap:Ethernet  HWaddr 00:04:5A:4A:CD:77
          inet addr:24.166.200.214  Bcast:255.255.255.255  Mask:255.255.240.0
          inet6 addr: fe80::204:5aff:fe4a:cd77/10 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
          RX packets:21171670 errors:1 dropped:0 overruns:0 frame:2
          TX packets:16604039 errors:0 dropped:0 overruns:0 carrier:0
          collisions:119520 txqueuelen:100
          RX bytes:4199358735 (4004.8 Mb)  TX bytes:3067991125 (2925.8 Mb)
          Interrupt:9 Base address:0x9c00

eth1      Link encap:Ethernet  HWaddr 00:04:5A:6E:CF:59
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::204:5aff:fe6e:cf59/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          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
          RX bytes:2683709402 (2559.3 Mb)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0xd800

- - - - - - - - - -

 cat /proc/interrupts
           CPU0
  0:   82504235          XT-PIC  timer
  1:        112          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  9:   63770876          XT-PIC  eth0 # no problems with this one
 10:   15423065          XT-PIC  eth1 # this one is misbehaving
 14:    4048812          XT-PIC  ide0
 15:          4          XT-PIC  ide1
NMI:          0
ERR:          0

- - - - - - - - - -

Also, related to this I believe, the firewall prints such messages out,
note the "OUT" field has no (printed) value:

SuSE-FW-DROP-NEW-CONNECT IN=eth0 OUT=
MAC=00:04:5a:4a:cd:77:00:05:74:f1:fc:54:08:00 SRC=24.59.147.238
DST=24.166.200.214 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=13019 DF PROTO=TCP
SPT=1167 DPT=17300 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402)

I hope this is enough info for someone to suggest something or know
what else to ask for.