public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Rob Sims <lkml-z@robsims.com>
Cc: Adrian Bunk <bunk@stusta.de>, Kyle Rose <krose@akamai.com>,
	linux-kernel@vger.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1
Date: Wed, 5 Sep 2007 10:22:30 +0100	[thread overview]
Message-ID: <20070905102230.10b0bdcf@oldman> (raw)
In-Reply-To: <20070730030130.GA6893@robsims.com>

On Sun, 29 Jul 2007 21:01:30 -0600
Rob Sims <lkml-z@robsims.com> wrote:

> On Thu, Jul 26, 2007 at 06:57:01PM +0200, Adrian Bunk wrote:
> > On Thu, Jul 26, 2007 at 11:16:36AM -0400, Kyle Rose wrote:
> > > >From http://www.krose.org/~krose/computing.html:
> > > 
> > > Since the sky2 driver continues to suck ass (which is a technical
> > > description for "it hangs all the time under load, at least on my
> > > hardware" :-) ), I've fixed the sk98lin driver to compile for
> > > linux-2.6.23-rc1. Those who continue to have problems with sky2 can
> > > still use 2.6.23-rc1, simply by doing the following:
> > >...
> > > Personally, I'd like to see sk98lin remain in the kernel proper until
> > > sky2 goes at least 6 months without reported problems.  The fact that I
> > > am not the only one still seeing issues is a clear indication that sky2
> > > (even with the recent patches in 2.6.23-rc1) is not yet ready to replace
> > > sk98lin.
> > >...
> > 
> > This sounds good in theory.
> > 
> > The practical problem with this approach is that there are always many 
> > people who use the old driver when the new driver doesn't work for them 
> > instead of reporting their problems with the new driver.
> > 
> > For these people a new driver will often suck when the old driver gets 
> > removed, but after the removal of the old driver they are finally forced 
> > to report their bugs resulting in a better new driver for everyone.
> > 
> > The sky2 driver is since nearly 2 years in the kernel and Stephen is 
> > usually quite good at handling bugs.
> 
> The driver still (2.6.20/sky2 1.13) hangs for me (more rarely than in
> the past), and cycling the module generally fixes the issues.  I have
> supplied all the information that Stephen has asked for, but still no
> resolution.  I am not complaining about the lack of a fix, but don't
> assume that all it takes to get sky2 working is adequate bug reports.  I
> have been and remain willing to test and assist debug, but after several
> dropped threads, I feel like the desire or ability to fix this issue
> isn't there (and remote debug of an intermittent hardware issue IS
> hard), and I didn't want to be a nuisance to someone that has no
> obligation to me to address the issue in the first place.
> 
> Stability has improved, it's just not there yet.
> 
> I'll switch to 1.16 soon, and respond to Stephen's request on netdev for
> current issues.
> -- 
> Rob

The only known outstanding problems on 2.62.22.6 of sky2 are:
 * problems with fibre PHY based systems
 * suspend/resume issues, missing multicast reinitalization, etc.
The previous stability problems have been addressed.

  reply	other threads:[~2007-09-05  9:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 15:16 sk98lin for 2.6.23-rc1 Kyle Rose
2007-07-26 16:28 ` Jan Engelhardt
2007-07-26 16:30   ` Kyle Rose
2007-07-26 16:41     ` Jan Engelhardt
2007-07-27  1:07       ` Kyle Rose
2007-07-26 16:57 ` Adrian Bunk
2007-07-26 22:58   ` Chris Stromsoe
2007-07-26 23:38   ` Bill Davidsen
2007-07-26 23:41     ` Jeff Garzik
2007-07-30  3:01   ` Rob Sims
2007-09-05  9:22     ` Stephen Hemminger [this message]
2007-09-05 19:42       ` James Corey
2007-09-05 21:04         ` Kyle Rose
2007-09-05 23:00           ` Stephen Hemminger
2007-09-08 17:44         ` Bill Davidsen
2007-09-08 19:11           ` Adrian Bunk
2007-09-09  2:42             ` Kyle Rose
2007-09-09  4:48               ` Willy Tarreau
2007-09-09 11:13               ` Adrian Bunk
2007-09-11  8:05                 ` Stephen Hemminger
2007-09-11 11:54                   ` Adrian Bunk
2007-09-11 14:29                     ` Bill Davidsen
2007-09-11 15:03                       ` Adrian Bunk
2007-09-11 22:37                         ` Willy Tarreau
2007-09-11 22:20                   ` James Corey
2007-09-09 12:54             ` Chris Stromsoe
2007-11-06 22:23               ` Stephen Hemminger
2007-11-07  1:42                 ` Chris Stromsoe
2007-09-10 14:32             ` Bill Davidsen
2007-09-10 15:39               ` Adrian Bunk
2007-09-11  4:23                 ` Kyle Moffett
2007-09-12 16:46       ` Torsten Kaiser
2007-07-26 19:17 ` Stephen Hemminger
2007-07-26 23:52 ` Bill Davidsen
2007-07-27  1:13   ` Kyle Rose

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=20070905102230.10b0bdcf@oldman \
    --to=shemminger@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=krose@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-z@robsims.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox