Problems with LinkSys 10/100 cards

[Adam Crews]

Hello all,

I have 2 machines both with 2 network cards in each.
Machine A's eth0 is a Intel eepro 100 card, running at 10mb connected to a
hub.  It works fine.  Machine B's eth0 is a Linksys pci ne2000 card that
also is working fine.

I added a Linksys 10/100 card to both machines as eth1 and have connected
them together with a crossover cable.  I am using the tulip.c:v0.90
version of the driver on a 2.0.36 kernel.  I have tried the tulip.c:v0.90h
version with the same results.

Both host's eth1 get the errors:
eth1: The transmitter stopped!  CSR5 is 2678016, CSR6 812e2202.
eth1: Changing PNIC configuration to full-duplex, CSR6 812e0200.

This happens shortly after starting the network interface, then again a
few more times in the first 5 minutes or so that the machine is up.

Pinging from host A to host B I get no response back to host A.  A
tcpdump on host B shows:

tcpdump: listening on eth1
23:07:34.306367 arp who-has 192.168.0.2 tell 192.168.0.1
23:07:34.306367 arp reply 192.168.0.2 is-at 0:a0:cc:25:58:c9
23:07:34.306367 192.168.0.1 > 192.168.0.2: icmp: echo request
23:07:35.306367 192.168.0.1 > 192.168.0.2: icmp: echo request
23:07:36.306367 211.192.168.0 > 1.192.168.0: (frag 21516:-20@4096) [ttl 0]
23:07:37.326367 209.192.168.0 > 1.192.168.0: (frag 21516:64@8192) [ttl 0]
23:07:38.326367 207.192.168.0 > 1.192.168.0: (frag 21516:-20@12288) [ttl
0]
23:07:39.326367 205.192.168.0 > 1.192.168.0: icmp: type-#2


A ping from host B to host a shows:

[doo@www doo]$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=-238747.-2 ms
wrong data byte #8 should be 0x8 but was 0x0
        13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28
29 2a 2b 2c 2d 2e 2f 30 31 32
        33 34 35 36 0 0 0 0 0 0 0 0 0 0 0 0
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.4 ms
wrong data byte #15 should be 0xf but was 0xe
        13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28
29 2a 2b 2c 2d 2e 2f 30 31 32
        33 34 35 36 0 0 0 0 0 0 0 0 0 0 0 0

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 2 packets received, 50% packet loss
round-trip min/avg/max = -238747.-2/214628991.4/0.4 ms



A tcpdump on host A shows normal packet responses.
22:56:01.527554 192.168.0.2 > 192.168.0.1: icmp: echo request
22:56:01.527554 192.168.0.1 > 192.168.0.2: icmp: echo reply
 

The tulip-diag tool on host A shows:

[doo@doo doo]$ sudo ./tulip-diag -p 0xfc00 -f -a -D
tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Digital DC21040 Tulip Tulip chip registers at 0xfc00:
  00008000 01ff0000 00450008 00096028 00096228 02660010 812e2202 0001ebef
  00000000 00000000 00096288 00094ce4 00000020 00000000 00000000 10000001
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, full-duplex.
 The transmit unit is set to store-and-forward.
 Port selection is MII 100baseTx scrambler, full-duplex.


and from B:
[doo@www doo]$ sudo ./tulip-diag  -p 0x6200 -a -f
tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Digital DC21040 Tulip Tulip chip registers at 0x6200:
  00008000 01ff0000 01000608 0031e028 0031e228 02660010 812e2202 0001ebef
  00000000 00000000 0031e308 0031e308 00000020 00000000 00000000 10000001
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, full-duplex.
 The transmit unit is set to store-and-forward.
 Port selection is MII 100baseTx scrambler, full-duplex.

Both cards have the link light, FD light and 100mb light showing green on
the back of the card.

Why am I getting the ping errors above?  How do I fix it?
I have changed cables with proven good one's.  I have swaped network cards
between the machines and get the same results on the same machines (the
problesm doesnt seem to follow the nic card).
I have even replaced both nic cards with new ones (and do some mixing and
matching to see if there was a posibility that 2 of the 4 nic hard I have
are bad.)  The problem remained the same.

Does anyone have any idea as to what is happening, and why?
Then how do I fix it?

-Adam