public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Linux Netdev" <netdev@vger.kernel.org>
Subject: Re: sky2 v1.7 rx error...
Date: Tue, 26 Sep 2006 13:44:17 -0700	[thread overview]
Message-ID: <20060926134417.689affb0@freekitty> (raw)
In-Reply-To: <6278d2220609261309v148618a4p4315d17aedc79a7d@mail.gmail.com>

On Tue, 26 Sep 2006 21:09:31 +0100
"Daniel J Blueman" <daniel.blueman@gmail.com> wrote:

> The server processor is a Pentium-M 1.7GHz (ondemand governor, from
> 0.6GHz -> 1.7GHz).
> 
> Gigabit path from server -> switch -> client. Client runs WinXP,
> Core2Duo 2.13GHz, Realtek RTL8168/8111 PCI-e NIC.
> 
> Flow contol enabled in both directions, both for client and server:
> sky2 lan0: Link is up at 1000 Mbps, full duplex, flow control both
> 
> Jumbo frames are in use on the tx side of server only - MTU 9000. I
> reproduced this with sky2 v1.7 with non-jumbo MTU 1500 frames too.
> 
> Let me know if there is any further information I can grab and/or any
> other settings/tweaks/patches I can try.
> 
> Dan
> 
> On 26/09/06, Stephen Hemminger <shemminger@osdl.org> wrote:
> > On Tue, 26 Sep 2006 18:58:40 +0100
> > "Daniel J Blueman" <daniel.blueman@gmail.com> wrote:
> >
> > > I got a this message with sky2 on 2.6.18 + the sky2 v1.7 patches - it
> > > has different status bits set than before (0x977d977d):
> > >
> > > kernel: sky2 lan0: rx error, status 0x377d377d length 0
> > >
> > > Great work so far though - this race takes a while to hit!
> > >
> > > Dan
> >
> > What speed processor? Are you using receive flow control? Are you
> > using Jumbo frames?
> >
> > --
> > Stephen Hemminger <shemminger@osdl.org>

Statistics?
	ethtool -S eth0

Does it hang after this? It looks like a receive fifo overflow, that happens
when the receive ring gets full.  You could try increasing RX_LE_SIZE from 512
to 1024.  That would eat more memory (510 packets) but might avoid the
problem.

Other possible solutions would be to reduce the coalescing timer values
with ethtool.
	ethtool -c eth1
	ethtool -C eth1 rx-usecs 10 rx-usecs-irq 10 rx-iframes-irq 4

-- 
Stephen Hemminger <shemminger@osdl.org>

  reply	other threads:[~2006-09-26 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6278d2220609261058y4b686489p813ef504f71bca4a@mail.gmail.com>
     [not found] ` <20060926115526.4bb5b99b@freekitty>
2006-09-26 20:09   ` sky2 v1.7 rx error Daniel J Blueman
2006-09-26 20:44     ` Stephen Hemminger [this message]
2006-09-26 22:19       ` Daniel J Blueman

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=20060926134417.689affb0@freekitty \
    --to=shemminger@osdl.org \
    --cc=daniel.blueman@gmail.com \
    --cc=netdev@vger.kernel.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