Intel EtherExpress 100 in DEC Alpha (UDB/Multia)

[Brendan Miller]

I just fired up my 100mbps hub, and connected my Digital UDB (Multia) to 
it using an Intel EtherExpress 100 in the PCI slot.  I get repeated messages 
in the log such as:

May 10 15:41:29 molybdenum kernel: eth0: Intel EtherExpress Pro 10/100 at 0x9000
, 00:A0:C9:DA:58:D9, IRQ 15.
May 10 15:41:29 molybdenum kernel:   Board assembly 689661-003, Physical connect
ors present: RJ45
May 10 15:41:29 molybdenum kernel:   Primary interface chip i82555 PHY #1.
May 10 15:41:29 molybdenum kernel:   General self-test: passed.
May 10 15:41:29 molybdenum kernel:   Serial sub-system self-test: passed.
May 10 15:41:29 molybdenum kernel:   Internal registers self-test: passed.
May 10 15:41:29 molybdenum kernel:   ROM checksum self-test: passed (0x24c9f043)
.
May 10 15:41:29 molybdenum kernel:   Receiver lock-up workaround activated.
May 10 15:41:39 molybdenum kernel: eth0: Transmit timed out: status 0050  0000 a
t 1/16 command 00020000.
May 10 15:41:39 molybdenum kernel: eth0: Trying to restart the transmitter...
May 10 15:42:09 molybdenum kernel: eth0: Transmit timed out: status 0050  0000 a
t 16/31 command 000c0000.
May 10 15:42:09 molybdenum kernel: eth0: Trying to restart the transmitter...
May 10 15:42:44 molybdenum kernel: eth0: Transmit timed out: status 0050  0000 a
t 36/51 command 00020000.
May 10 15:52:09 molybdenum kernel: eth0: Transmit timed out: status 0050  0000 a
t 1/16 command 00020000.
May 10 15:52:09 molybdenum kernel: eth0: Trying to restart the transmitter...
May 10 15:52:38 molybdenum PAM_pwdb[403]: (login) session closed for user root
May 10 15:52:44 molybdenum kernel: eth0: Transmit timed out: status 0050  0000 a
t 20/35 command 00020000.
May 10 15:52:44 molybdenum kernel: eth0: Trying to restart the transmitter...

and with it, temporary network outages to this machine.

I notice from the mailing list archives that this is a historic problem.
but I did not deduce a solution from my reading.  Being a UDB, this is 
a single processor machine.  I am using kernel version 2.2.3 and eepro100.c
version 1.06.

What is the problem?

Please advise,

Brendan