receive errors

[Eric Ding]

Hi Donald,

>>>>> Donald Becker <becker@cesdis1.gsfc.nasa.gov> writes:

> CRC errors (0x0002), and occasionally dribble bits (0x0004) with the CRC
> errors.

> This looks like a problem with corrupted receive packets.
> This can sometimes be caused by a duplex mismatch, with the local end
> being in full duplex while the remote end is half duplex.

> The reverse mismatch is characterized by transmit out-of-window errors, Tx
> error bit 0x0200

> The next time use 'tulip-diag -a' to report the duplex.  You can retrigger
> autonegotiation by momentarily unplugging the cable.

thanks for the reply.  Here's what tulip-diag reports, so I don't think the
duplex is the problem:

[root@jlu ericding]# ./tulip-diag -p 0xe400 -a -f
tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Digital DC21040 Tulip Tulip chip registers at 0xe400:
  00008000 01ff0000 ffffffff 009cb820 009cba20 02660010 814e2002 0001ebef
  00000000 00000000 009cbaa0 003bb424 00000025 00000000 00000000 10000001
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, half-duplex.
 The transmit threshold is 72.
 Port selection is MII 100baseTx scrambler, half-duplex.

Any other suggestions?

Thanks,
Eric