From: Rik van Riel <riel@redhat.com>
To: netdev@vger.kernel.org
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>,
Matt Carlson <mcarlson@broadcom.com>,
Michael Chan <mchan@broadcom.com>, KVM list <kvm@vger.kernel.org>
Subject: TG3, kvm, ipv6 & tso data corruption bug?
Date: Wed, 28 Oct 2009 10:46:55 -0400 [thread overview]
Message-ID: <4AE8595F.1080404@redhat.com> (raw)
I have been tracking down what I thought was a KVM related network
issue for a while, however it appears it could be a hardware issue.
The symptom is that data in network packets gets corrupted, before
the checksum is calculated. This means the remote host can get
corrupted data, with no way to calculate it (except application
level checksums). Luckily ssh has such checksums, so my rsync over
ssh backup script discovered this issue.
On a very regular basis, I got this message from ssh:
Corrupted MAC on input.
I have played around a bit and narrowed it down to the following:
ipv4 => no problem
ipv6 w/o tso => no problem
ipv6 with tso => occasional data corruption
Disabling tso with ethtool -K eth0 tso off makes the problem stop.
I am running Fedora 12's 2.6.31.1-56.fc12.x86_64 kernel, with the
following hardware:
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761
Gigabit Ethernet PCIe (rev 10)
I do not know enough about the network layer to know whether this is
fixable in software or whether TSO offloading for ipv6 should just
be disabled on this model.
--
All rights reversed.
next reply other threads:[~2009-10-28 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 14:46 Rik van Riel [this message]
2009-10-28 16:32 ` TG3, kvm, ipv6 & tso data corruption bug? Matt Carlson
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=4AE8595F.1080404@redhat.com \
--to=riel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).