All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Grozdan <neutrino8@gmail.com>
Cc: linux-kernel@vger.kernel.org, shemminger@vyatta.com
Subject: Re: sky2 rx length errors
Date: Sun, 20 Sep 2009 20:54:23 +0200	[thread overview]
Message-ID: <20090920185423.GA30562@1wt.eu> (raw)
In-Reply-To: <c5bd819b0909201146t35d921afh267c9430b114e23e@mail.gmail.com>

On Sun, Sep 20, 2009 at 08:46:59PM +0200, Grozdan wrote:
(...)
> Thanks Willy :)
> 
> What I'm still wondering a bit though is the fact that I've never seen
> it behave like that for the past 3 years I've been using it. Only
> recently, with upgrading my kernel to 2.6.30 and later on to 2.6.31
> (self-compiled, sources taken from the openSUSE build service) it
> started to behave like that. In the past I also used older kernels (of
> course) like 2.6.27.x and 2.6.29 and never encountered this. So I'm a
> bit uncertain as to whether it's actually something in the kernel that
> makes it behave like that or that there's a HW problem that suddenly
> occurred or got exposed...

Unless you changed the switch port it is connected to, I agree this
sounds strange. I have also wondered if those issues could be caused
by temperature rising on the chip. I don't know if any recent change
could cause such environmental differences to occur :-/

Regards,
Willy


  reply	other threads:[~2009-09-20 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 13:41 sky2 rx length errors Grozdan
2009-09-20  6:35 ` Andrew Morton
2009-09-20 18:05   ` Stephen Hemminger
2009-09-20 18:16     ` Grozdan
2009-09-20 18:34       ` Willy Tarreau
2009-09-20 18:46         ` Grozdan
2009-09-20 18:54           ` Willy Tarreau [this message]
     [not found]     ` <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com>
2009-09-21  1:46       ` 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:
  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=20090920185423.GA30562@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neutrino8@gmail.com \
    --cc=shemminger@vyatta.com \
    /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.