1) 01:05.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 08)
kernels: 2.2.19 and 2.4.4
drivers used: kernel eepro100 (2.2.19 and 2.4.4) and intel e100 (2.4.4)
symptoms: the system would spontaneously reboot under heavy NFS traffic,
with no console or /var/log/messages reports.
This could be reliably reproduced by mounting an exported directory, and
looping "find /mounted/directory -depth -print | xargs cat >/dev/null"
2) SMC EZNET 10/100 nic, using a realtek chipset
kernels: 2.4.4
drivers used: kernel 8139too
symptoms: the system would hang under heavy network traffic, and need to
be powercycled backed to life.
ping -f could cause it, as could the test above.
Nothing of interest to report via console or syslog.
I've currently replaced these cards with the Netgear FA310 series, using
the tulip driver (01:0b.0 Ethernet controller: Lite-On Communications Inc
LNE100TX (rev 20)) and have had no problems, so being able to help in
testing would probably be more difficult.
-
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/