Re: [2.6 patch] the scheduled sk98lin removal

[Chris Stromsoe <cbs@cts.ucla.edu>]

On Tue, 10 Jul 2007, Stephen Hemminger wrote:

> On Tue, 10 Jul 2007 12:44:35 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
>
> > Adrian Bunk wrote:
> > > This patch contains the scheduled removal of the sk98lin driver.
> > >
> > > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > Stephen -- ACK?
>
> Yes.  Existing driver is dead, if there are any ancient boards that don't
> work with skge, I haven't heard any complaints in at least a year.
> As a fallback users, can always go with vendor driver.

I have a several SK-9872s that do not work reliably with skge but work 
fine with sklin.  The SK-9872 is a dual port card.  Doing the following 
causes a hard lock:

modprobe bonding miimon=100 mode=active-backup
modprobe skge
ifup bond0
ifdown bond0

This happens with every version of skge I've tested, including whatever is 
in 2.6.22.  /etc/network/interfaces contains:

iface bond0 inet static
        network 192.168.1.0
        address 192.168.1.1
        broadcast 192.168.1.255
        netmask 255.255.255.0

        up ifenslave bond0 eth0 eth1
        down ifenslave -d bond0 eth0 eth1


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: <access denied>




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