public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 04 Feb 2005 23:53:34 -0500	[thread overview]
Message-ID: <4204514E.2040905@stinkfoot.org> (raw)
In-Reply-To: <20050204050822.GT2493@waste.org>

Matt Mackall wrote:
> 
> Ok, reproduceable without ssh makes narrowing this down much easier.
> Are you seeing errors on the interface? No would indicate problems
> post CRC checking on the receive side. Do errors happen in both
> directions? If not, it may be CPU speed-related or specific to a given
> NIC - swap them if they're not onboard. 
> 
> The next test is to send patterns. Try sending yourself a gigabyte of:
> 
> #include <stdio.h>
> 
> int main(void)
> {
>         int i;
> 
>         for (i = 0; i < 0x10000000; i++) {
>                 fwrite(&i, 4, 1, stdout);
>         }
> }
> 
> If there's some sort of partial DMA transfer going on, this should
> make it evident.
> 

No errors reported on either interface.

Interesting results, in one direction though.  It seems highly likely 
the problem is only with the 82545EM as I couldn't get a botched 
transfer FROM it to the 82547EI after 20 or so attempts, (both of these 
are onboard unfortunately so no swapping).  Several transfers TO it did 
yield bad files, though (using my big 1.6G gzipped tarball).

Now, on to the patterns.  I didn't get a _single_ failure in either 
directions using what that code snippet generated in over 20 attempts. 
Perhaps we're failing on larger amounts of more complex data?

-Ethan

  parent reply	other threads:[~2005-02-05  4:52 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
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       ` Ethan Weinstein [this message]
2005-02-04  6:03     ` e1000, sshd, and the infamous "Corrupted MAC on input" 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=4204514E.2040905@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