From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Rick Jones" <rick.jones2@hp.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: Re: e1000 tcp checksum incorrect, x86 64b
Date: Fri, 28 Sep 2007 13:39:34 -0400 [thread overview]
Message-ID: <9e4733910709281039n75be6264rdb34124d8c30ab44@mail.gmail.com> (raw)
In-Reply-To: <46FD2D3B.4050605@hp.com>
On 9/28/07, Rick Jones <rick.jones2@hp.com> wrote:
> Herbert Xu wrote:
> > Jon Smirl <jonsmirl@gmail.com> wrote:
> >
> >>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
> >
> >
> > Wireshark is broken. It needs to know TP_STATUS_CSUMNOTREADY
> > means that the checksum is partial and will only be completed
> > when the hardware sends the packet out.
> >
> > Alternatively disable checksum offload with ethtool.
>
> Or take the packet traces "outboard" of the NIC somewhere/somehow.
>
> What problem(s) led to your taking the packet trace in the first place?
I was working on the Ethernet driver for another embedded system
attached to the box. I noticed these errors going to my NSLU2 which I
thought was working ok. But now I know they are not real errors.
Ethernet driver for MPC5200 in embedded system still has some
problems. It is being discussed on linuxppc-embedded.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2007-09-28 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 3:50 e1000 tcp checksum incorrect, x86 64b Jon Smirl
2007-09-28 4:08 ` Herbert Xu
2007-09-28 16:35 ` Rick Jones
2007-09-28 17:39 ` Jon Smirl [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=9e4733910709281039n75be6264rdb34124d8c30ab44@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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).