eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11)

Robbert Kouprie (robbert@radium.jvb.tudelft.nl)
Thu, 11 Oct 2001 14:29:56 +0200


Hi all,

I can confirm that the known bug in the Intel EtherExpress Pro/100
adapter is still not worked around in recent kernels. The bug only
manifests itself when the card is operating on 10 Mbit half duplex. On
100 Mbit there are no problems. The problem is that after the device
received certain amount of traffic (between 80 and 130 Mb in my tests)
the device will lockup on new connections. Processes start to hang after
this and logging in is impossible. The only solution is to reset the
interface (using a previously logged in root session) and reboot the
system.

This is tested on :
Linus kernels:
- 2.4.5
- 2.4.10-pre2
- 2.4.10
- 2.4.11pre6
- 2.4.11
- 2.4.11 with eepro100.c from ac kernel 2.4.10ac11 (minor diffs)

Again, on 100 Mbit there are no more problems.

This is my relevant dmesg output:

eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:E8:A2:02, IRQ 17.
Board assembly 749658-005, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xdbd8681d).

cat /proc/pci part:
Bus 0, device 13, function 0:
Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev
9).
IRQ 17.
Master Capable. Latency=32. Min Gnt=8.Max Lat=56.
Non-prefetchable 32 bit memory at 0xda020000 [0xda020fff].
I/O at 0xc800 [0xc83f].
Non-prefetchable 32 bit memory at 0xda000000 [0xda01ffff].

These are taken from the current setup on 100 Mbit.

Regards,
- Robbert Kouprie, System Administrator, The Netherlands

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/