Re: e1000 tcp checksum incorrect, x86 64b

2007-09-28 Thread Jon Smirl
On 9/28/07, Rick Jones <[EMAIL PROTECTED]> wrote: > Herbert Xu wrote: > > Jon Smirl <[EMAIL PROTECTED]> 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 co

Re: e1000 tcp checksum incorrect, x86 64b

2007-09-28 Thread Rick Jones
Herbert Xu wrote: Jon Smirl <[EMAIL PROTECTED]> 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, Re

Re: e1000 tcp checksum incorrect, x86 64b

2007-09-27 Thread Herbert Xu
Jon Smirl <[EMAIL PROTECTED]> 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

e1000 tcp checksum incorrect, x86 64b

2007-09-27 Thread Jon Smirl
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 prob