Good morning all,

I'm experiencing difficulties with a Marvell NIC (marketed as 8062 -
on the chip 88E8062 is stamped - lspci calls it an unknown device 4347).
It is not recognized by the sk98lin driver of recent kernels.

The sk98lin driver provided by Marvell Technologies seems to work (no
extensive testing done though), but is at this time only available for 
Linux kernels before 2.6.14.

The sky2 driver version 0.7 (floating around as a patch) seemed to work
OK (flow control isn't supported) in RHFC4's 2.6.14 at first, even fast
(as measured using ttcp), but after light load over several hours (some 
2.4e6 packets) a few hosts (we have a bunch of identical machines, see
below) fell of the net, i.e. no packet is received or transmitted any-
more (observed with tcpdump). In the kernel's message buffer I found 
following:
--8<--
hw tcp v4 csum failed
hw tcp v4 csum failed
hw tcp v4 csum failed
hw tcp v4 csum failed
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
[.. many of those ..]
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
-->8--

I tried again, now using Linux 2.6.16-rc2 from kernel.org which comes
with version 0.13 of the sky2 driver. Again, it seemed to work OK (still
no flow control though) at first, but after some 2.4e6 packets a few hosts
(not the same though) fell of the net again. In the kernel message buffer
I found this time:
--8<--
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
NETDEV WATCHDOG: eth0: transmit timed out
sky2 transmit interrupt missed? recovered
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
-->8--
In all cases, no errors were reported by `netstat -i` (no corrupted 
packets).

The hosts are Blades of a Penguin Computing BladeRunner, equipped with
dual Intel Xeon EMT64 CPUs, Intel 7500 chipset and the aforementioned
Marvel 88E8062 network controller.

If I can provide further information or if the problem is already known 
and fixed, please let me know.

best regards
    Guenther
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to