From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Petr Vandrovec <petr@vandrovec.name>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Unbreak sky2 on 88E8039 with current git
Date: Sun, 3 Feb 2008 10:08:47 -0800 [thread overview]
Message-ID: <20080203100847.3022883e@extreme> (raw)
In-Reply-To: <47A51168.5040301@vandrovec.name>
On Sat, 02 Feb 2008 16:57:12 -0800
Petr Vandrovec <petr@vandrovec.name> wrote:
> Stephen Hemminger wrote:
> > On Sat, 2 Feb 2008 11:52:43 +0100
> > Petr Vandrovec <petr@vandrovec.name> wrote:
> >
> >> Hello,
> >> since I synced my tree to Linus's one two days ago, sky2's packet receiption
> >> dies almost instantly. Device still transmits packets, but no receive.
> >> Fortunately fix is simple, unfortunately I do not know why fix works...
> >>
> >> Commit f03b865491c2f30f2a4d77cdafc69c978ceb38a0 (sky2: align IP header on Rx
> >> if possible) stopped aligning receive buffers on devices which do not need
> >> HANG_CHECK. Unfortunately there is at least one device (mine, Yukon FE, rev 3)
> >> which is not happy if receive buffer is not aligned. I have no idea which
> >> other chips/revisions are affected as well.
> >>
> >> Without patch 'ping -f -b 192.168.101.255' RX count stops incrementing in less
> >> than 50 packets. With patch in place it can run like before, for hours...
> >> Box is an AMD rev F processor, with nVidia's MCP61 chipset.
> >> Petr
> >
> > I don't have a Yukon FE, but I believe that the Yukon FE does have a ram
> > buffer, so you HANG_CHECK should be enabled for that device. You can check
> > by running:
> > ethtool -d eth0 | grep 'Ram Buffer'
> > With ram buffer (like XL, EC)
> >
> > # ethtool -d eth0 | grep 'Ram Buffer'
> > Ram Buffer 0x18
> >
> > No ram buffer (like EC-U, FE+, ...)
> > # ethtool -d eth0 | grep 'Ram Buffer'
> > Ram Buffer 0x00
>
> Some small one (if it is size):
>
> gwy:~# ethtool -d eth0 | grep 'Ram'
> Ram Buffer 0x01
>
> I've never observed hang on that device, and I have it for over year. I
> stress it sufficiently to kill EC rev 2 I have in the notebook when I
> copy some data between these two boxes, but this FE never hung.
> Petr
>
Since the ram buffer is only 4K on this chip, 2K is used for rx.
You probably could make it hang by making CPU busy and hitting it
with 2 packets whose total length is was 1K each.
--
Stephen Hemminger <stephen.hemminger@vyatta.com>
next prev parent reply other threads:[~2008-02-03 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 10:52 [PATCH] Unbreak sky2 on 88E8039 with current git Petr Vandrovec
2008-02-02 20:02 ` Stephen Hemminger
2008-02-03 0:57 ` Petr Vandrovec
2008-02-03 18:08 ` Stephen Hemminger [this message]
2008-02-05 3:45 ` [PATCH] sky2: fix for Yukon FE (regression in 2.6.25) Stephen Hemminger
2008-02-05 18:32 ` Jeff Garzik
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=20080203100847.3022883e@extreme \
--to=shemminger@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petr@vandrovec.name \
/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.