From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Felix Radensky <felix@allot.com>
Cc: netdev@oss.sgi.com
Subject: Re: hw tcp v4 csum failed on 2.4.23-rc2 with e100
Date: Wed, 26 Nov 2003 01:04:00 +0100 [thread overview]
Message-ID: <20031126010359.B1264@sygehus.dk> (raw)
In-Reply-To: <3FBDE9BF.2070909@allot.com>; from felix@allot.com on Fri, Nov 21, 2003 at 12:32:31PM +0200
On Fri, Nov 21, 2003 at 12:32:31PM +0200, Felix Radensky wrote:
> Hi,
>
> I keep getting tons of this messages with 2.4.23-rc2
> and e100 driver:
>
> hw tcp v4 csum failed
> hw tcp v4 csum failed
I just got (e100 with i82559, kernel 2.4.22-bk45)
Nov 25 23:17:13 linddaase kernel: udp v4 hw csum failure.
Nov 25 23:20:51 linddaase kernel: udp v4 hw csum failure.
Nov 25 23:26:59 linddaase kernel: udp v4 hw csum failure.
Nov 25 23:26:59 linddaase kernel: UDP: bad checksum. From 130.233.41.46:47064 to 80.161.68.244:1026 ulen 421
while playing XPilot on kallio.cs.hut.fi. Two false alarms and one real
checksum failure. What the deal is with the false alarms is a good question
since no useful information about the packets is logged.
--
Regards,
Rask Ingemann Lambertsen
parent reply other threads:[~2003-11-26 0:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3FBDE9BF.2070909@allot.com>]
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=20031126010359.B1264@sygehus.dk \
--to=rask@sygehus.dk \
--cc=felix@allot.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).