[tulip] Netgear FA310-TX NIC problems

[A.J. Rossini]

On Mon, 10 Jul 2000, Donald Becker wrote:

> On Mon, 10 Jul 2000, A.J. Rossini wrote:
> 
> > I'm seeing similar problems as previously reported, with the FA310TX 
> 
> Which version of the FA310TX?

Here's what I can tell:

# ./tulip-diag -m -m 
tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xde00.
 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 72.
 MII PHY found at address 1, status 0x782d.
 MII PHY #1 transceiver registers:
   3000 782d 0040 6212 01e1 0021 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   5000 0000 0000 0000 0000 0000 0300 0000
   003c 8006 0f00 ff00 002c 4000 0080 000b.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:10:18:--:--:--, model 33 rev. 2.
   No specific information is known about this transceiver type.
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0021: 10baseT.
   Negotiation did not complete.

> What is the detection message?

>From dmesg/kernel boot:

tulip.c:v0.92 4/17/2000  Written by Donald Becker <becker@scyld.com>
  http://www.scyld.com/network/tulip.html
eth0: Lite-On 82c168 PNIC rev 32 at 0xcc843f00, 00:A0:CC:65:E6:AE, IRQ 10.
eth0:  MII transceiver #1 config 3000 status 7829 advertising 01e1.

> > Thoughts?  I've been running the drivers from the 2.2.17pre kernel
> > (Debian potato/woody), which is the 0.91g-ppc version.
> 
> You should try v92.
>    http://www.scyld.com/network/tulip.html
>       ftp://www.scyld.com/pub/network/tulip.c
> 

Tried and failed with the same problem.

Using tulip debug=1, I've been getting the lock-up regularly using
"strobe" against a local machine.  This knocks out networking to all
machines, and I start getting the following error:

	 eth0: Transmit timeout using MII device.

At this point, the above diagnostics look like:

 http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xde00.
 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 'Waiting for Tx to finish'.
  The transmit threshold is 72.
 MII PHY found at address 1, status 0x782d.
 MII PHY #1 transceiver registers:
   3000 782d 0040 6212 01e1 0021 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   5000 0000 0000 0000 0000 0000 0400 0000
   003c 8006 0f00 ff00 002c 4000 0080 000b.
 Basic mode control register 0x3000: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:10:18:--:--:--, model 33 rev. 2.
   No specific information is known about this transceiver type.
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0021: 10baseT.
   Negotiation did not complete.

(note that the top portion of tulip-diag scrolled off my screen too fast,
but it basically said the same thing as before, wrt tulip diag.)

Any more thoughts/approaches to try?

best,
-tony

----
A.J. Rossini
rossini@blindglobe.net		BlindGlobe Networks
rossini@biostat.washington.edu	UW Biostat/Center for AIDS Research