From: Arno Griffioen <arno@usn.nl>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be (Geert Uytterhoeven)
Cc: davem@dm.cobaltmicro.com, 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 11:13:26 +0100 (MET) [thread overview]
Message-ID: <199812221013.LAA23494@superluminal.usn.nl> (raw)
In-Reply-To: <Pine.LNX.4.03.9812221039490.5727-100000@mercator.cs.kuleuven.ac.be> from "Geert Uytterhoeven" at Dec 22, 98 11:01:13 am
> > BTW, do all of the PPC's which exhibit the behavior use the same
> > ethernet controller?
>
> Yes, we all have Tulip boards (I think >95% of the PPC users have Tulip
> boards). And the message on linux-kernel about checksum errors on ARM related
> to Tulip made me suspicious at well...
Suggestion:
Perhaps you should try some tests with an Amiga/PPC machine. That definitely
doesn't use the Tulip board, but is PPC based. Can't help you there yet
though as Linux/PPC dies with a machine-check when I try to access
the brain-dead ISA NE2000 in my machine.
Should give some clue about either the PPC checksum-computation or
the ethernet card doing 'nasty things'.
Bye Arno.
--
Internet Exchange Europe B.V.Fax: +31-70-3630470 | One disk to rule them all,
Lange Voorhout 9 Tel: +31-70-3600379 | One disk to bind them,
2514EA Den Haag +--------------------------------+ One disk to hold the files
The Netherlands | * END OF TRANSMISSION * | And in the darkness grind 'em
----------------+--------------------------------+------------------------------
[[ 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 10:13 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
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 [this message]
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=199812221013.LAA23494@superluminal.usn.nl \
--to=arno@usn.nl \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=davem@dm.cobaltmicro.com \
--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).