From: "Aurélien GÉRÔME" <ag@roxor.be>
To: linux-kernel@vger.kernel.org
Subject: Re: iMac G3 IPv6 issue
Date: Sun, 12 Sep 2004 22:59:51 +0200 [thread overview]
Message-ID: <20040912205951.GB11293@caladan.roxor.be> (raw)
In-Reply-To: <1095011851.4995.54.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
On Sun, Sep 12, 2004 at 06:57:31PM +0100, David Woodhouse wrote:
> On Sun, 2004-09-12 at 15:39 +0200, Aurélien GÉRÔME wrote:
> > I put IPv6 support, but the console is flooded by a lot of:
> > hw tcp v6 csum failed
> > However, IPv6 works, and IPv4 packets do not have this kind of issue.
> > The network card is a Sun Gem. It is kind of weird to see bad packets.
>
> I use the sungem in a similar machine with IPv6, and haven't seen any
> problems. Can you tcpdump from a different machine on the network and
> confirm whether these reported bad checksums really are happening or if
> it's the fault of the hardware/driver?
I have 2 machines on the same switch and an IPv6 ssh connection between
them.
"tcpdump -a -i eth0 -v" on both machines shows [tcp sum ok].
The ssh link is an IPv6 one, arwen is the faulty machine, and aragorn a
sane one.
arwen has also a ppp0 interface, no infamous [bad tcp cksum ....!]
appears, on lo interface too. All is reported [tcp sum ok].
But during this time, the kernel keeps flooding the console with these
"hw tcp v6 csum failed"...
Moreover, like I said, the IPv6 networking works fine.
In that case, is it the driver fault?
I wonder if it is possible to print the checksum and the interface with
the LIMIT_NETDEBUG(printk(KERN_DEBUG "hw tcp v6 csum failed\n"));.
Bests.
--
_,met$$$$$gg. Aurélien GÉRÔME
,g$$$$$$$$$$$$$$$P. Free Software Developer
,g$$P"" """Y$$.". Unix Sys & Net Admin
,$$P' `$$$.
',$$P ,ggs. `$$b: Web: https://www.roxor.be/
`d$$' ,$P"' . $$$ Mail: ag@roxor.be
$$P d$' , $$P GPG Key ID: 03E1A172
$$: $$. - ,d$$'
$$; Y$b._ _,d$P' )) GNU (( / Linux
Y$$. `.`"Y$$$$P"' // \\
`$$b "-.__ ((__,-"""-,__)) .---.
`Y$$b `--)~ ~(--` / \
`Y$$. Debian .-'( )`-. \.@-@./
`$$b. `~~`@) (@`~~` /`\_/`\
`Y$$b. | | // _ \\
`"Y$b._ | | | \ )|_
`"""" (8___8) /`\_`> <_/ \
`---` \__/'---'\__/
BOFH excuse #88: Boss' kid fucked up the machine
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-12 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 13:39 Aurélien GÉRÔME
2004-09-12 13:51 ` Aurélien GÉRÔME
2004-09-12 17:57 ` David Woodhouse
2004-09-12 20:59 ` Aurélien GÉRÔME [this message]
2004-09-12 22:58 ` David S. Miller
2004-09-12 23:17 ` Aurélien GÉRÔME
2004-09-12 23:28 ` David S. Miller
2004-09-12 23:46 ` Aurélien GÉRÔME
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=20040912205951.GB11293@caladan.roxor.be \
--to=ag@roxor.be \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®