From: Stephen Hemminger <shemminger@osdl.org>
To: foo@porto.bmb.uga.edu
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bad UDP checksums with 2.6.9
Date: Thu, 4 Nov 2004 09:09:25 -0800 [thread overview]
Message-ID: <20041104090925.188fc471@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <20041104062834.GE12763@porto.bmb.uga.edu>
On Thu, 4 Nov 2004 01:28:34 -0500
foo@porto.bmb.uga.edu wrote:
> On Thu, Nov 04, 2004 at 12:48:38AM -0500, foo wrote:
> > 'm seeing the same problem as in:
> > Message-Id: 20041020191203.GA14356@merlin.emma.line.org
> > or http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/1310.html
> >
> > I just upgraded a machine from 2.6.5 to 2.6.9, and when the amanda
> > backup server contacts it, it sometimes replies with a UDP packet with a
> > bad checksum. I'm using e1000 here, so it seems to not be related to
> > the ethernet driver. I have a binary tcpdump if anyone's interested.
>
> I don't know why I didn't think of this at first, but I have another
> identical machine that I upgraded at the same time that doesn't have the
> problem.
>
> Here's a diff between their .configs - albarino is the one having
> trouble. Maybe CONFIG_PACKET_MMAP? If someone can point me at a likely
> config option to change I'll boot a new kernel for the next backup run
> Friday night.
Do both machines have the same exact version of E1000? Some support
TCP Segmentation Offload (TSO) and some do not.
You might try turning off tso (and tx checksuming) and see if that
is related.
ethtool -K eth0 tso off
next prev parent reply other threads:[~2004-11-04 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 5:48 foo
2004-11-04 6:28 ` foo
2004-11-04 17:09 ` Stephen Hemminger [this message]
2004-11-04 17:39 ` Sven Schuster
2004-11-04 20:29 ` foo
2004-11-05 11:40 ` Matthias Andree
2004-11-05 9:40 ` Martin Josefsson
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=20041104090925.188fc471@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=foo@porto.bmb.uga.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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®