All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: sky2 still broken in 2.6.20.3
Date: Wed, 21 Mar 2007 18:01:27 -0400	[thread overview]
Message-ID: <4601AB37.7070302@redhat.com> (raw)
In-Reply-To: <20070321144052.02eb2ac7@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> On Wed, 21 Mar 2007 16:26:53 -0400
> Chuck Ebbert <cebbert@redhat.com> wrote:
> 
>> Transmit timeouts and locked-up adapters still occur in kernel
>> 2.6.20.3.
> 
> There is more changes in 2.6.21-rc4 please try that.

Yes, but I have to figure out how to get those to apply to
2.6.20.3. I was hoping you'd do that. :)

> I am still getting reports of timeouts with that code but
> it does recover better. It may be the case that with hardware
> flow control transmits can take an indefinite period so increasing
> the timeout value could help.
> 
>> It looks like the patch that was applied to 2.6.20.2
>> is not enough. Unfortunately that one isn't the same as what
>> went upstream. Looks like it needs to be reverted, then the two
>> upstream patches applied?
> 
> Until, unless the problem is reproducible with my hardware
> there is not much that can be done. I'll add the better recovery
> logic to for next stable cycle, but still not clear what causes
> all the timeouts.

I have a bug report and tester:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227420


  reply	other threads:[~2007-03-21 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 20:26 sky2 still broken in 2.6.20.3 Chuck Ebbert
2007-03-21 21:40 ` Stephen Hemminger
2007-03-21 22:01   ` Chuck Ebbert [this message]
2007-03-22 19:18     ` Stephen Hemminger
2007-04-06 16:43 ` 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=4601AB37.7070302@redhat.com \
    --to=cebbert@redhat.com \
    --cc=linux-kernel@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 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.