Network problems with 2.0.31

Darren Reed (darrenr@cyber.com.au)
Sat, 8 Nov 1997 23:00:00 +1100 (EST)

Whilst happily compiling away over NFS (had three other simultaneous
compiles of the same s/w happening over NFS too), my Linux box decided
NFS was hung to my NFS server. All the others seemed ok (but none of
the others were Linux...)

anyway, after a bit it restarted and dumped this out:

NFS server sunos4 not responding, still trying.
eth0: transmit timed out, tx_status 88 status e000.
eth0: Transmitter encountered 16 collisions -- network cable problem?
Flags; bus-master 1, full 1; dirty 114449 current 114465.
Transmit list 00087238 vs. 00087238.
0: @00087228 length 80000062 status 80000062
1: @00087238 length 800000be status 000000be
2: @00087248 length 8000009a status 0000009a
3: @00087258 length 80000053 status 00000053
4: @00087268 length 8000004f status 0000004f
5: @00087278 length 80000036 status 00000036
6: @00087288 length 80000055 status 00000055
7: @00087298 length 8000009a status 0000009a
8: @000872a8 length 80000062 status 00000062
9: @000872b8 length 80000053 status 00000053
10: @000872c8 length 80000062 status 00000062
11: @000872d8 length 80000062 status 00000062
12: @000872e8 length 80000062 status 00000062
13: @000872f8 length 80000062 status 00000062
14: @00087308 length 80000062 status 00000062
15: @00087318 length 80000062 status 80000062
eth0: Freeing Tx ring entries:NFS server sunos4 OK.

FYI, eth0:

eth0: 3Com 3c900 Boomerang 10Mbps/Combo at 0x6400, 00:60:97:d1:d4:51, IRQ 10
eth0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248.

(using the 3c59x.c from 2.0.31).

I've never seen this before, from anything and I've had that box (which is
presently running Linux) run Solaris2/FreeBSD/NetBSD in exactly the same
scenario. Needless to say I'm not particularly amused by the hangup...

Darren