From: Ethan Weinstein <lists@stinkfoot.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e1000, sshd, and the infamous "Corrupted MAC on input"
Date: Thu, 03 Feb 2005 23:16:37 -0500 [thread overview]
Message-ID: <4202F725.8040509@stinkfoot.org> (raw)
In-Reply-To: <20050203070415.GC17460@waste.org>
Matt Mackall wrote:
> 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
next prev parent reply other threads:[~2005-02-04 4:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 3:44 e1000, sshd, and the infamous "Corrupted MAC on input" Ethan Weinstein
2005-02-03 7:04 ` Matt Mackall
2005-02-04 4:16 ` Ethan Weinstein [this message]
2005-02-04 5:08 ` Matt Mackall
2005-02-04 5:54 ` Has anyone dumped udev for devfs? Anthony DiSante
2005-02-05 4:53 ` e1000, sshd, and the infamous "Corrupted MAC on input" Ethan Weinstein
2005-02-04 6:03 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4202F725.8040509@stinkfoot.org \
--to=lists@stinkfoot.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox