From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org,
linux-m68k@lists.linux-m68k.org
Subject: Re: TCPv4 checksum errors
Date: Tue, 22 Dec 1998 01:35:55 -0800 [thread overview]
Message-ID: <199812220935.BAA09166@dm.cobaltmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.03.9812220933440.5727-100000@mercator.cs.kuleuven.ac.be> (message from Geert Uytterhoeven on Tue, 22 Dec 1998 10:21:58 +0100 (CET))
Date: Tue, 22 Dec 1998 10:21:58 +0100 (CET)
From: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
> of a specific packet with a bad checksum generated by Linux/PPC?
cassandra kernel: TCPv4 bad checksum from 10.0.24.8:03ff to 10.0.24.4:0201, len=20/20/40
(10.0.24.8 is CHRP, 10.0.24.4 is Amiga)
My suggestion is that since you can reproduce it, you should add code
next to this printk statement which dumps the entire packet in HEX to
the console. Then you can see what and who is at fault and where.
If the packet is sufficiently small you can walk the checksum
algorithm by hand and verify it for this test case.
In any event this should allow you to say a lot more about this
situation, I hear about it a lot and if I were a PPC or m68k developer
I would not let it go for this long, especially if I could reproduce
it on my own friggin' machine!
BTW, do all of the PPC's which exhibit the behavior use the same
ethernet controller?
Later,
David S. Miller
davem@dm.cobaltmicro.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-22 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-21 21:49 TCPv4 checksum errors Geert Uytterhoeven
1998-12-22 3:07 ` Paul Mackerras
1998-12-22 7:21 ` Martin Costabel
1998-12-22 9:21 ` Geert Uytterhoeven
1998-12-22 9:35 ` David S. Miller [this message]
1998-12-22 10:01 ` Geert Uytterhoeven
1998-12-22 10:11 ` David S. Miller
1998-12-22 10:38 ` Geert Uytterhoeven
1998-12-22 10:13 ` Arno Griffioen
1998-12-23 9:14 ` Geert Uytterhoeven
1998-12-23 13:23 ` Gabriel Paubert
1998-12-23 21:58 ` Alan Cox
1998-12-24 7:36 ` David S. Miller
1998-12-28 9:20 ` Andreas Schwab
1998-12-28 13:04 ` Alan Cox
1998-12-28 13:12 ` Andreas Schwab
1998-12-24 3:57 ` Paul Mackerras
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=199812220935.BAA09166@dm.cobaltmicro.com \
--to=davem@dm.cobaltmicro.com \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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).