[tulip-bug] Probems with FastLine-II FO (100BaseFX Card)

[Christoph Heine]

Hi!

I've two problems with two FastLine-II FO Cards:

a) There is something wrong with 'TX packets' and 'TX errors'

eth2      Link encap:Ethernet  HWaddr 00:00:CB:55:06:12
          inet addr:172.20.252.4  Bcast:172.20.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:237758 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3048 errors:206356 dropped:0 overruns:1carrier:206356
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0x9000

While this seems only to be cosmetically, the other problem is more
noticeable:

b)
Packetloss, from 2% up to 4%. (Which does not occur when I use a
eepro100 with a media converter)

Any ideas what it could be? I also tried the de4x5 driver with de-facto
negative result.

Greetings,
	Christoph Heine


Here is the output from varouis tools/messages around the card:

dmesg:
Linux Tulip driver version 0.9.14 (February 20, 2001)
PCI: Found IRQ 12 for device 00:0a.0
eth1: Digital DS21143 Tulip rev 65 at 0x9400, 00:00:CB:55:06:67, IRQ
12.
eth1:  EEPROM default media type MII 100baseTx.
eth1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
block.
eth1:  Index #1 - Media AUI (#2) described by a 21143 reset method (5)
block.
eth1:  MII transceiver #1 config 2100 status 7809 advertising 0001.
eth1:  Advertising 01e1 on PHY 1, previously advertising 0001.
eth1:  Advertising 01e1 (to advertise is 01e1).
PCI: Found IRQ 10 for device 00:0b.0
PCI: The same IRQ used for device 00:11.0
eth2: Digital DS21143 Tulip rev 65 at 0x9000, 00:00:CB:55:06:12, IRQ
10.
eth2:  EEPROM default media type MII 100baseTx.
eth2:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
block.
eth2:  Index #1 - Media AUI (#2) described by a 21143 reset method (5)
block.
eth2:  MII transceiver #1 config 2100 status 7809 advertising 0001.
eth2:  Advertising 01e1 on PHY 1, previously advertising 0001.
eth2:  Advertising 01e1 (to advertise is 01e1).
eth0: 0 multicast blocks dropped.
tulip-diag:
tulip-diag.c:v2.07 3/31/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0x9400.
 Port selection is MII, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
  The NWay status register is 000000c6.
  Internal autonegotiation state is 'Autonegotiation disabled'.
Index #2: Found a Digital DS21143 Tulip adapter at 0x9000.
 Port selection is MII, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 512.
  The NWay status register is 000000c6.
  Internal autonegotiation state is 'Autonegotiation disabled'.
 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.


mii-diag.c:v2.00 4/19/2000  Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   2100 780d 7810 0003 0001 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 4000 0104 3808 0010 0000 0002
   0001 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x2100: Auto-negotiation disabled, with
 Speed fixed at 100 mbps, full-duplex.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Link partner information information is not exchanged when in fixed
speed mode.