From: Andreas Schwab <schwab@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: jonmason@us.ibm.com, cramerj@intel.com, netdev@oss.sgi.com,
netdev-bounce@oss.sgi.com
Subject: Re: Bad UDP checksum with 82540EM
Date: Sun, 08 Feb 2004 14:09:36 +0100 [thread overview]
Message-ID: <jeznbtg1kf.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040208074643.482ab4c7.ak@suse.de> (Andi Kleen's message of "Sun, 8 Feb 2004 07:46:43 +0100")
Andi Kleen <ak@suse.de> writes:
> On Sat, 07 Feb 2004 23:42:21 +0100
> Andreas Schwab <schwab@suse.de> wrote:
>
>> Jon D Mason <jonmason@us.ibm.com> writes:
>>
>> > This probably isn't helpful, but it sounds like a hardware error. Is the
>> > error occurring on multiple/all HP adapters, or only one?
>>
>> I've also seen it with a HP branded BCM5701 on IA64, but also with a
>> Broadcom BCM5702 on AMD64 (both using the tg3 driver). It seems like
>> broken UDP checksumming is rather common. :-(
>
> It could be still a software bug. When hardware checksumming is available
> the UDP packets use a slightly different path through the stack.
>
> Could you perhaps test if the problem occurs in a 32bit box with the
> same NIC ? Maybe it is some 64bit problem somewhere in software.
Just tested with a "3Com 3C996B-T 1000Base-T" (BCM5701 based, with tg3
driver) on an Athlon. It shows the same bug, and disabling HW
checksumming on tx fixes it. So it doesn't look like a 64bit issue.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-02-08 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 13:35 Bad UDP checksum with 82540EM Andreas Schwab
2004-02-07 21:37 ` Jon D Mason
2004-02-07 22:42 ` Andreas Schwab
2004-02-08 6:46 ` Andi Kleen
2004-02-08 13:09 ` Andreas Schwab [this message]
[not found] <101E0EB68A545748974019DC227C554007CBDD@orsmsx406.jf.intel.com>
2004-02-09 0:50 ` Andreas Schwab
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=jeznbtg1kf.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ak@suse.de \
--cc=cramerj@intel.com \
--cc=jonmason@us.ibm.com \
--cc=netdev-bounce@oss.sgi.com \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.