netdev
[Top] [All Lists]

Re: Bad UDP checksum with 82540EM

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: Bad UDP checksum with 82540EM
From: Andreas Schwab <schwab@xxxxxxx>
Date: Sun, 08 Feb 2004 14:09:36 +0100
Cc: jonmason@xxxxxxxxxx, cramerj@xxxxxxxxx, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx
In-reply-to: <20040208074643.482ab4c7.ak@xxxxxxx> (Andi Kleen's message of "Sun, 8 Feb 2004 07:46:43 +0100")
References: <OFE5352D34.67E10D98-ON87256E33.00725857-86256E33.0076C481@xxxxxxxxxx> <je3c9mv7ea.fsf@xxxxxxxxxxxxx> <20040208074643.482ab4c7.ak@xxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux)
Andi Kleen <ak@xxxxxxx> writes:

> On Sat, 07 Feb 2004 23:42:21 +0100
> Andreas Schwab <schwab@xxxxxxx> wrote:
>
>> Jon D Mason <jonmason@xxxxxxxxxx> 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@xxxxxxx
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."

<Prev in Thread] Current Thread [Next in Thread>