Messages in this thread |  | | | Date | Thu, 26 Jul 2007 15:58:39 -0700 (PDT) | | From | Chris Stromsoe <> | | Subject | Re: sk98lin for 2.6.23-rc1 |
| |
On Thu, 26 Jul 2007, 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.
I have a number of SK-9844 "SK-NET GE-SX dual link" cards. skge has never worked with the cards.
The following sequence locks up the machine completely (power cycle to get it back) with 2.6.22.1:
fresno:~# modprobe skge fresno:~# ip li set eth2 up fresno:~# ip li set eth2 down fresno:~# ip li set eth3 up
This works just fine:
fresno:~# rmmod skge 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
eth2 and eth3 are ports off the sk-9844.
I've been reporting the problem since March. If sk98lin is removed, I won't have networking.
-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/
|  |