LKML Archive on
help / color / mirror / Atom feed
From: Stephen Hemminger <>
To: Petr Vandrovec <>
Subject: Re: [PATCH] Unbreak sky2 on 88E8039 with current git
Date: Sat, 2 Feb 2008 12:02:03 -0800	[thread overview]
Message-ID: <20080202120203.5387d1cb@extreme> (raw)
In-Reply-To: <>

On Sat, 2 Feb 2008 11:52:43 +0100
Petr Vandrovec <> 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' 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
Stephen Hemminger <>

  reply	other threads:[~2008-02-02 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 10:52 Petr Vandrovec
2008-02-02 20:02 ` Stephen Hemminger [this message]
2008-02-03  0:57   ` Petr Vandrovec
2008-02-03 18:08     ` Stephen Hemminger

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080202120203.5387d1cb@extreme \ \ \ \ \
    --subject='Re: [PATCH] Unbreak sky2 on 88E8039 with current git' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).