Made a pure 2.4.13-ac5 kernel. Linux system is P3 Asus CUV4X-E with
D-Link DGE550T. MS is an old Compaq P with DGE500T. Switch is 3-Com
3C16468 (copper, unmanaged). Attached is various system information.
   Samba (2.2.2) is used to mount the MS drive on Linux, and to mount
the Linux drive on MS.
   Moving a file from Linux to MS on MS results in a timeout
immediately:
	NETDEV WATCHDOG: eth0: transmit timed out
	eth0: Transmit timed out, TxStatus 570080
	NETDEV WATCHDOG: eth0: transmit timed out
	eth0: Transmit timed out, TxStatus 0000
The last TXStatus of 0000 is repeated until reboot. The first status is
not always the same, although the ?70080 seems consistent.
   Moving a file from Linux to MS on Linux results in a timeout much
later, but the symptom is the same.
   Using 2.4.13-ac3 I can move the file on the Linux system to MS
without problems. Moving it using the MS system always results in an
immediate timeout. The 2.4.13-ac3 always has nVidia's driver loaded, and
has RML's latency patch. The 2.4.13-ac5 was made with no other patches,
and booted without X. The modules loaded in the system are attached.
Kernels compiled with 2.59.3, rest of system with 3.0.1. MTU is 1500.