lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176747.59824.qm@web90412.mail.mud.yahoo.com>
Date:	Tue, 11 Sep 2007 15:20:32 -0700 (PDT)
From:	James Corey <ploversegg@...oo.com>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>
Cc:	Kyle Rose <krose@...se.org>, Bill Davidsen <davidsen@....com>,
	James Corey <ploversegg@...oo.com>,
	Rob Sims <lkml-z@...sims.com>, linux-kernel@...r.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1


--- Stephen Hemminger
<shemminger@...ux-foundation.org> wrote:

> On Sun, 9 Sep 2007 13:13:26 +0200
> Adrian Bunk <bunk@...nel.org> wrote:
> 
> > On Sat, Sep 08, 2007 at 10:42:20PM -0400, Kyle
> Rose wrote:
> > > 
> > > > You are a regular reader of linux-kernel, and
> therefore the sk98lin 
> > > > removal can hardly be a surprise for you. If
> you prefer whining over 
> > > > helping to improve the kernel that's your
> choice...
> > > >   
> > > In my case the issue is simply one of
> practicality: I cannot go to the
> > > data center 5 times per day to reboot my colo
> box.  Therefore, I run
> > > sk98lin.  It's really that simple.
> > 
> > When did you report this bug the first time?
> > 
> > What we need is that people when testing a new
> kernel they plan to use 
> > test the new drivers *and report the bugs if they
> run into any*.
> > 
> > What could we have done so that you reported your
> bug without removing 
> > the sk98lin driver?
> > 
> > > Kyle
> > 
> > cu
> > Adrian
> 
> 
> There are several different problems in this thread:
> 1. The removal of old sk98lin driver caused some
> users to be forced to use
>     skge. These users have uncovered issues with the
> dual port fiber based versions
>     of the board.  
>     Short term: The sk98lin driver should be
> restored to previous state, 
>        and the PCI table should be used to limit the
> usage to only fiber systems.
>        If Adrian doesn't do it, I'll do it when I
> return from Germany.
>     Long term: I have fiber based board (thanks
> ebay) on the way to resolve
>        skge bug.
> 
> 2. Sky2 driver has it's own fiber based problems. 
> Solve these after skge fiber.
> 
> 3. Sky2 doesn't have as many workarounds for
> hardware problems as vendor sk98lin
>     driver.
> -


Hm, hope I didn't trigger a religious debate. When
you get to the point of working on the SKY2 driver
problem with DGE-550SX (Syskonnect SK-9S81) also
known as the "hw csum failure" issue, I'll be 
glad to test a patch or take debug data. Til then,
I'll stay out of the way.

-J





      ____________________________________________________________________________________
Shape Yahoo! in your own image.  Join our Network Research Panel today!   http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ