From: Tony Battersby <tonyb@cybernetics.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: BUG: sky2: hw csum failure with dual-port copper NIC on SMP
Date: Tue, 13 Nov 2007 17:57:12 -0500 [thread overview]
Message-ID: <473A2BC8.7000909@cybernetics.com> (raw)
In-Reply-To: <20071113141414.0959735a@freepuppy.rosehill>
Stephen Hemminger wrote:
> I can reproduce the problem under load with only a single port on 2.6.23.
> I haven't been able to reproduce it on 2.6.24-rc2 (latest) but that maybe
> because of either insufficient stress or another bug fix correcting the
> problem. There is an issue with Yukon XL updating the receive status index
> before updating the receive status structure, that is now fixed in 2.6.24.
> The fix is:
>
> commit ab5adecb2d02f3688719dfb5936a82833fcc3955
> Author: Stephen Hemminger <shemminger@linux-foundation.org>
> Date: Mon Nov 5 15:52:09 2007 -0800
>
> sky2: status ring race fix
>
> The D-Link PCI-X board (and maybe others) can lie about status
> ring entries. It seems it will update the register for last status
> index before completing the DMA for the ring entry. To avoid reading
> stale data, zap the old entry and check.
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
> Signed-off-by: Jeff Garzik <jeff@garzik.org>
The kernel I tested (2.6.24-rc2-git3) has this patch in it already.
Perhaps that is why the problem happens less frequently with that
kernel, but it didn't fix it entirely.
Do you want the test program I am using? It is a pretty basic
send()/recv() program, ~650 lines of C.
Tony
next prev parent reply other threads:[~2007-11-13 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 17:51 BUG: sky2: hw csum failure with dual-port copper NIC on SMP Tony Battersby
2007-11-13 22:14 ` Stephen Hemminger
2007-11-13 22:57 ` Tony Battersby [this message]
2007-11-13 23:27 ` Stephen Hemminger
2007-11-14 15:37 ` Tony Battersby
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=473A2BC8.7000909@cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).