From: Jamie Lokier <jamie@shareable.org>
To: James Stevenson <james@stev.org>
Cc: Doruk Fisek <dfisek@fisek.com.tr>, linux-kernel@vger.kernel.org
Subject: Re: hw tcp v4 csum failed
Date: Mon, 28 Jul 2003 20:05:43 +0100 [thread overview]
Message-ID: <20030728190543.GA10426@mail.jlokier.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0307280135420.4847-100000@jlap.stev.org>
James Stevenson wrote:
> > I am getting "hw tcp v4 csum failed" errors using a BCM5701 ethernet
> > adapter with the tigon3 driver in a vanilla 2.4.20 kernel.
> Its probably a problem releated to the cable or surrounding
> interference on the cable.
This is an ethernet adapter. It means that interference problems
should cause CRC32 errors, and the packets will be dropped/logged at
the MAC layer, and the TCP checksum not checked. The MAC layer CRC32
is strong enough that TCP checksum errors should be exceedingly rare,
unless the interference is very bad and a very large number of packes
are being submitted.
Perhaps the error message is not really indicating TCP checksum errors?
-- Jamie
prev parent reply other threads:[~2003-07-28 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 7:02 hw tcp v4 csum failed Doruk Fisek
2003-07-27 22:26 ` David S. Miller
2003-07-28 0:37 ` James Stevenson
2003-07-28 19:05 ` Jamie Lokier [this message]
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=20030728190543.GA10426@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=dfisek@fisek.com.tr \
--cc=james@stev.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;
as well as URLs for NNTP newsgroup(s).