From: Matt Mackall <mpm@selenic.com>
To: Ethan Weinstein <lists@stinkfoot.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e1000, sshd, and the infamous "Corrupted MAC on input"
Date: Wed, 2 Feb 2005 23:04:15 -0800 [thread overview]
Message-ID: <20050203070415.GC17460@waste.org> (raw)
In-Reply-To: <42019E0E.1020205@stinkfoot.org>
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
> Hey all,
>
> I've been having quite a time with the e1000 driver running at gigabit
> speeds. Running it at 100Fdx has never been a problem, which I've done
> done for a long time. Last week I picked up a gigabit switch, and that's
> when the trouble began. I find that transferring large amounts of data
> using scp invariably ends up with sshd spitting out "Disconnecting:
> Corrupted MAC on input." After deciding I must have purchased a bum
> switch, I grabbed another model.. only to get the same error.
> 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.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-02-03 7:04 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 [this message]
2005-02-04 4:16 ` Ethan Weinstein
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=20050203070415.GC17460@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@stinkfoot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.