[tulip] Parity error on 2nd Tulip card
Fri Feb 7 10:52:01 2003
On Fri, 7 Feb 2003, Abe Ward Kabakoff wrote:
> 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
What driver version?
What is the detection message?
> 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?
> 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 (firstname.lastname@example.org)
> 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.
Donald Becker email@example.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Scyld Beowulf cluster system
Annapolis MD 21403 410-990-9993