public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ethan Weinstein <lists@stinkfoot.org>
To: linux-kernel@vger.kernel.org
Subject: e1000, sshd, and the infamous "Corrupted MAC on input"
Date: Wed, 02 Feb 2005 22:44:14 -0500	[thread overview]
Message-ID: <42019E0E.1020205@stinkfoot.org> (raw)

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.

Both systems are 2.6.10, with 4k stacks, and regparm enabled. system 1 
has an onboard Intel 82547EI, system 2 has an onboard Intel 82545EM, 
both have NAPI enabled... Oddly, running the nics at 100Fdx does not 
generate this error no matter how much pressure I put on them. I've 
found a lot of scuttlebutt regarding these problems with sshd on the 
net, but this appears a hardware/driver problem.  There's mention of a 
specific problem with e1000 here: 
http://www.psc.edu/networking/projects/hpn-ssh  but no apparent resolution.

Any suggestions are greatly appreciated.

-E

             reply	other threads:[~2005-02-03  3:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  3:44 Ethan Weinstein [this message]
2005-02-03  7:04 ` e1000, sshd, and the infamous "Corrupted MAC on input" Matt Mackall
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=42019E0E.1020205@stinkfoot.org \
    --to=lists@stinkfoot.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox