eepro100 on alpha, linux 2.1

[Gus Buerkle]

Donald,

Regarding my attempt to use the eepro100 drivers under linux-alpha
2.1.122,

I compiled the eepro-diag program under 2.0.32 and ran it on the 2.1.122
kernel running the v0.36 driver.  (It failed to compile under a
development kernel) Here are the results:

[root@marzen /root]# ./eepro-diag -f -e -e -a -m
eepro100-diag.c:v0.07 2/25/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Intel 82557 EtherExpressPro100B adapter at 0x8000.
i82557 chip registers at 0x8000:
  00000050 4065b018 00000000 00080002 14378462 00000600
  No interrupt sources are pending.
   The transmit unit state is 'Suspended'.
   The receive unit state is 'Ready'.
EEPROM contents:
  d000 1564 4ad0 0000 0000 0080 2200 0000
  1a92 0481 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 6b93
 The EEPROM checksum (should be 0xbaba) is 0xdd5a.
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:D0:64:15:D0:4A.
  Receiver lock-up bug exists. (The driver work-around *is* implemented.)
  Board assembly 1a9204-129, Physical connectors present:
  Primary interface chip i82553-C PHY #0.

What about this EEPROM checksum?

Here's the logged messages when the network interface crashes:
<dates are erroneous>
Aug 28 10:43:46 dunkel kernel: eth0: Transmit timed out: status 0050
command 0000.
Aug 28 10:43:46 dunkel kernel: eth0:  Tx timeout  fill index 53098
scavenge index 53084.
Aug 28 10:43:46 dunkel kernel:     Tx queue  000ca000 000ca000 000ca000
000ca000 000ca000 000ca000 000ca000 000ca000 000ca000 400ca000 000ca000
000ca000 000c0000 000ca000
 000ca000 000ca000.
Aug 28 10:43:46 dunkel kernel:     Rx ring  00000003 00000003 00000003
00000003 00000003 00000003 00000003 00000003 00000003 00000003 00000003
c0000003 00000003 00000003 00000003 00000003.
Aug 28 10:43:46 dunkel kernel: eth0: Trying to restart the transmitter...

>From this point the network is unresponsive, and the only way to bring it
back is to unload the eepro module and then reinsert it.  Simply bringing
the eth0 interface down and up will not do it.

Thanks for checking this out.  

Gus Buerkle