linux-kernel - Re: sk98lin for 2.6.23-rc1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Nov 2007 14:23:20 -0800
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Chris Stromsoe <cbs@....ucla.edu>
Cc:	Adrian Bunk <bunk@...nel.org>, Bill Davidsen <davidsen@....com>,
	James Corey <ploversegg@...oo.com>,
	Rob Sims <lkml-z@...sims.com>, Kyle Rose <krose@...mai.com>,
	linux-kernel@...r.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1

On Sun, 9 Sep 2007 05:54:45 -0700 (PDT)
Chris Stromsoe <cbs@....ucla.edu> wrote:

> On Sat, 8 Sep 2007, Adrian Bunk wrote:
> > On Sat, Sep 08, 2007 at 01:44:20PM -0400, Bill Davidsen wrote:
> >
> >> Haven't tried later kernels, don't intend to, while no network is 
> >> really secure, it not really useful.
> >
> > 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...
> 
> I've been trying to migrate off sk98lin to skge since earlier this year, 
> without success, starting with 2.6.18 or .19.
> 
> I have several of these cards in production using the sk98lin driver:
> 
> fresno:~# lspci -vv -s 02:01
> 02:01.0 Ethernet controller: SysKonnect SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link) (rev 11)
>          Subsystem: SysKonnect SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>          Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>          Latency: 64 (5750ns min, 7750ns max), Cache Line Size: 32 bytes
>          Interrupt: pin A routed to IRQ 22
>          Region 0: Memory at febfc000 (32-bit, non-prefetchable) [size=16K]
>          Region 1: I/O ports at e800 [size=256]
>          Expansion ROM at febc0000 [disabled] [size=128K]
>          Capabilities: [48] Power Management version 1
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                  Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>          Capabilities: [50] Vital Product Data
> 
> They are dual port SX fiber.  Both ports are connected.  If I do this:
> 
> fresno:~# modprobe skge
> fresno:~# ip li set eth2 up
> fresno:~# ip li set eth2 down
> fresno:~# ip li set eth3 up
> 
> the system locks up and I have to power cycle it.  The order doesn't 
> matter (if I do eth3 up/down, then eth2 up kills it).
> 
> I don't have any problems with sk98lin.  This works fine:
> 
> fresno:~# modprobe sk98lin RlmtMode=DualNet
> fresno:~# ip li set eth2 up
> fresno:~# ip li set eth2 down
> fresno:~# ip li set eth3 up
> fresno:~# ip li set eth3 down
> 
> 
> I am more than happy to test various driver changes, and have tried a few 
> suggested patches but nothing has worked so far.  I would like to be using 
> skge instead of sk98lin, but so far haven't had any success.

Please test 2.6.24-rc1 (or -rc2) because there were several fixes for skge
that made it work correctly for dual port fiber board. The worst bug in skge
was that it configured the ram buffer incorrectly.

I just submitted these for next 2.6.23.X stable release as well

-- 
Stephen Hemminger <shemminger@...ux-foundation.org>
-
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/