From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, langus@timpanogas.org
Cc: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: 3ware Escalade problems
Date: Thu, 2 Aug 2001 15:02:16 -0700 [thread overview]
Message-ID: <20010802150216.A25975@vger.timpanogas.org> (raw)
In-Reply-To: <20010801185836.B22548@vger.timpanogas.org> <E15SHUV-0000SM-00@the-village.bc.nu> <20010802142631.A25795@vger.timpanogas.org>
In-Reply-To: <20010802142631.A25795@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Thu, Aug 02, 2001 at 02:26:31PM -0700
Alan,
On a related problem, we are seeing packet checksum corruption with both
the 3Com and Intel Gigabit ethernet adapters when a ping -f -s > 1472 packet
fllods are initiated. The sniffers report packets with corrupted checksum
information. I am copying Larry Angus on this email since he has all
the sniffer traces. These problems show up on 2.2 and 2.4 kernels.
We noticed several emails in the archive regarding this problem, but
no fixes reported. What's disturbing regarding this issue is that
hardware checksum errors are being generated which results in the
packets being lost.
Larry - please provide the traces and documentation you have discovered
to Alan regarding this problem.
Jeff
next prev parent reply other threads:[~2001-08-02 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 18:14 Scott Ransom
2001-08-01 21:39 ` Jeff V. Merkey
2001-08-02 0:26 ` Alan Cox
2001-08-02 1:40 ` Jeff V. Merkey
2001-08-02 0:40 ` Alan Cox
2001-08-02 1:58 ` Jeff V. Merkey
2001-08-02 12:22 ` Alan Cox
2001-08-02 21:26 ` Jeff V. Merkey
2001-08-02 22:02 ` Jeff V. Merkey [this message]
2001-08-02 14:19 ` 3ware Escalade problems? Adaptec? Michael Rothwell
[not found] <53B208BD9A7FD311881A009027B6BBFB9EADC7@siamese>
2001-08-01 18:51 ` 3ware Escalade problems Scott Ransom
[not found] <53B208BD9A7FD311881A009027B6BBFB9EADCC@siamese>
2001-08-02 1:38 ` Jeff V. Merkey
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=20010802150216.A25975@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@timpanogas.org \
--cc=langus@timpanogas.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
all inboxes | Powered by JetHome®