Problems with DEC Ethernet Controller

From: Scott Brown (sbrown@lamar.ColoState.EDU)
Date: Tue May 09 2000 - 13:08:42 EST


I'm having major problems getting a DEC21040 ethernet controller up and
running stable, and I don't know what to try next. I have the same
problem on 4 DEC alphastation 500 / 400 machines.

The problem is that the eth0 interface just seems to hang, as in ping
results in 100% packet loss. I'm not able to reproduce this, but it
occurs on a frequent basis.

Here's the output at boot time:

**** dmesg | tail output ****

> tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
> eth0: Digital DC21040 Tulip rev 36 at 0x9000, 00:00:F8:21:A8:9C, IRQ 29.
> eth0: No link beat found.

So I thought it's not detecting the media. Forcing the module to use our
media type (10base2) does not produce any change in the behavior.

**** ifconfig output ****

> eth0 Link encap:Ethernet HWaddr 00:00:F8:21:A8:9C
> inet addr:129.82.149.1 Bcast:129.82.149.63 Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8030 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6940 errors:0 dropped:0 overruns:0 carrier:0
> collisions:51 txqueuelen:100
> Interrupt:29 Base address:0x9000

**** cat /proc/net/dev output ****

> Inter-| Receive
> face |bytes packets errs drop fifo frame compressed multicast
> lo: 1680 24 0 0 0 0 0 0
> eth0: 733433 8029 0 0 0 0 0 0

> Inter-| Transmit
> face |bytes packets errs drop fifo colls carrier compressed
> lo: 1680 24 0 0 0 0 0 0
> eth0: 1047243 6939 0 0 0 51 0 0

**** ./tulip-diag -af output ****

> tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DC21040 Tulip adapter at 0x9000.
> Digital DC21040 Tulip chip registers at 0x9000:
> fff88400 ffffffff ffffffff 4773f058 4773f0d8 fc660000 fffc2002 ffff8065
> fffe0000 7fffff00 ffffffff ffffffff ffffffc0 ffff8f09 ffff0705 ffff0006
> Port selection is half-duplex.
> Transmit started, Receive started, half-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit unit is set to store-and-forward.

**** ./tulip-diag -ee output ****

> tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DC21040 Tulip adapter at 0x9000.
> Port selection is half-duplex.
> Transmit started, Receive started, half-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit unit is set to store-and-forward.
> EEPROM contents:
> 0000 21f8 a0a6 e496 96e4 a6a0 f821 0000
> 0000 21f8 a0a6 e496 00ff aa55 00ff aa55
> 0000 21f8 a0a6 e496 96e4 a6a0 f821 0000
> 0000 21f8 a0a6 e496 00ff aa55 00ff aa55
> e71e ffff ffff ffff ffff ffff ffff ffff
> ffff ffff ffff ffff ffff ffff ffff ffff
> ffff ffff ffff ffff ffff ffff ffff ffff
> ffff ffff ffff ffff ffff ffff ffff ffff
> ID block CRC 0x90 (vs. 00).
> Full contents CRC 0x917d (read as 0xffff).

**** ./tulip-diag -mm output ****

> tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DC21040 Tulip adapter at 0x9000.
> Port selection is half-duplex.
> Transmit started, Receive started, half-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit unit is set to store-and-forward.
> No MII transceivers found!



This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:29 EST