From: "Jon Smirl" <jonsmirl@gmail.com>
To: netdev <netdev@vger.kernel.org>
Subject: e1000 tcp checksum incorrect, x86 64b
Date: Thu, 27 Sep 2007 23:50:21 -0400 [thread overview]
Message-ID: <9e4733910709272050t65e76312k52fd7493b899071d@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
App is writing seven bytes to the socket. Socket write timeout expires
and the seven bytes are sent. The checksum is not getting inserted
into the packet. It is set to a constant 0x8389 instead of the right
value. App is gmpc 0.15.4.95, Revision: 6794
Attached Wireshark packet trace show the problem. e1000 is 192.168.1.4
64bit, Q6600. Dell Dimension 9200
Checksum is being computed ok for file copy traffic.
Problem was in rc7 too, I upgraded to current git to see if it was
fixed and it isn't
Wireshark is 0.99.4 from Ubuntu in case it is the problem.
--
Jon Smirl
jonsmirl@gmail.com
[-- Attachment #2: checkerr --]
[-- Type: application/octet-stream, Size: 9733 bytes --]
next reply other threads:[~2007-09-28 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 3:50 Jon Smirl [this message]
2007-09-28 4:08 ` e1000 tcp checksum incorrect, x86 64b Herbert Xu
2007-09-28 16:35 ` Rick Jones
2007-09-28 17:39 ` Jon Smirl
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=9e4733910709272050t65e76312k52fd7493b899071d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=netdev@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).