Bill Fink <[EMAIL PROTECTED]> writes: > It may also be a useful test to disable hardware TSO support > via "ethtool -K ethX tso off".
All suggestions here on the list, i.e. checking for flow control, duplex, cable problems, etc. don't explain (at least to me) why LF sees file corruption. How can a corrupted frame pass the TCP checksum check? Does TCP use the hardware checksum of the NIC if available? AFAICS, this would be the only way for a corrupt frame to make it into the file. But Bill already suggested this and LF reported that it didn't make a difference. A few months ago I had hadware problems with an embedded device, where transmission from the NIC via the PCI bus to the CPU had some bits flipped. But tcpdump clearly showed the TCP checksum errors and also TCP recognized the errors and the connection was stalled. And, BTW, we also observed an increasing percentage of corrupted frames with increasing traffic on that interface, i.e. increasing load on the PCI bus. So I would run tcpdump -s0 and watch for "incorrect checksum" messages. urs - 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
