public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Kyle Rose <krose@akamai.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1
Date: Thu, 26 Jul 2007 19:52:01 -0400	[thread overview]
Message-ID: <46A933A1.7050601@tmr.com> (raw)
In-Reply-To: <46A8BAD4.8020004@akamai.com>

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:
> 
Bless you, extends my update capability for another version. ;-)

However, Ingo posted a patch for the thread "network dies after random 
time" which probably didn't make it into rc1. In all fairness applying 
that might fix the problem, it's possible if unlikely that the new 
driver tickles a bug the stable sk98lin driver didn't.

Does skge work for your hardware? Based on a sample size of one (four to 
go) everything worked for me except NFS, jumbo packets work with tcp, 
not with udp. I don't have everything nailed down enough for a proper 
bug report, it's just something to note. In truth there's little to 
choose between tcp and udp for machines in the same room, I could live 
with skge.

haven't tried shy2, there was a build failure on my last server build, 
won't look at it until Monday.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2007-07-26 23:50 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
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 [this message]
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=46A933A1.7050601@tmr.com \
    --to=davidsen@tmr.com \
    --cc=krose@akamai.com \
    --cc=linux-kernel@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