FA310TX TX lockup

Geoffrey Wossum gpw0341@omega.uta.edu
Sun Jan 23 17:07:38 2000

Hello all,

I have two computers with Netgear FA310TX cards.  One computer works fine,
the other computer's NIC will stop responding after a while.  Bringing the
interface down and then back up will fix it for a little bit, but then it
will do it again.  When this happens, tulip-diag says "Waiting for TX to

I swapped the cards between the computers, and get the same results, so it
must be a driver/configuration problem, not hardware.  The problem
computer has had all the kernels from 2.2.9 to 2.2.14 on it, and all had
the problem.  It is currently using tulip.c:v0.91g-ppc from kernel 2.2.14

Here is the output from tulip-diag when the lockup occurs:
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xd400.
 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.

Other information:
RedHat 6.0
Kernel 2.2.14
Computers are connected together through a 10Base-T hub
Non-working computer is a Pentium 200 MMX, ASUS TX97 mobo
No port/IRQ conflicts visible from /proc

Other interesting note:
The working computer's NIC always goes to 0xb400, IRQ 10.
The non-working computer's NIC always goes to 0xd400, IRQ 11.

Thanks in advance for any help anyone can give me!

Geoffrey Wossum
Project AKO - http://rover1.uta.edu/~ako
Internet Imperialists - http://inetimperial.sourceforge.net
To unsubscribe send a message body containing "unsubscribe"
to linux-tulip-request@beowulf.org