On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:...
Finally, I used a crossover cable between the two boxes, which resulted in the same error from sshd again.
Well ssh isn't an especially good test as it's hard to debug.
Try transferring large compressed files via netcat and comparing the results. eg:
host1# nc -l -p 2000 > foo.bz2
host2# nc host1 2000 < foo.bz2
If the md5sums differ, follow up with a cmp -bl to see what changed.
Then we can look at the failure patterns and determine if there's some data or alignment dependence.
Excellent tip, thanks. I was able to reprodce the problem several times using this technique with nc, however the problem was intermittent (as nasty problems like this often are). I used a 1.3G gzipped tarball and experienced several botched transfers along with a few good ones. To be fair, I also switched back to 100Fdx and repeated; I didn't get a single failure at this speed over 25 or so runs.
The results of two cmp's are here:
http://www.stinkfoot.org/e1000tests.out
What next?
-Ethan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
