Actually, some of us are working on the 2.0.x kernel series still....we just
don't make a lot of noise about it :)
>But I still think some serious work needs to go into the 2.0 kernel
>since it is suppose to be the stable kernel but isn't.
Work is going into it :)
>The amount of attention given 2.0 by the gurus is so small compared to the
>effort going on in 2.1 that I would feel more comfortable running and
>updating a 2.1 bleeding-edge kernel because I know problems will get
>fixed quickly.
>
>My post on the 2.0.32 lockup and the others I've seen have pretty much
>been ignored (or so it seems since there hasn't been further discussion
>on whats wrong and how to fix it).
Actually, not all of them have gone unanswered, and they haven't gone
ignored. So far we've been able to develope the following two items in the
patterns that I've seen anyway. Either the aic7xxx driver is involved, or
the 3c59x driver is involved. There may be those out there that don't fit
this pattern, but I don't recall your particular hardare listing. As to the
aic7xxx driver, the patch found on the LMP web site has been reported to
help with the lock-ups (and well it should, I fixed several infinite loop
problems in the stock driver with that patch as well as added bounding to
the majority of the loops in case anything goes haywire and creates a
circumstance I haven't been able to create yet). As for the 3c59x driver,
well, that's just a fine and dandy can of worms. I have yet to hear of a
single version of that driver that works on *all* the cards it is suppossed
to support.....
If you want to see the problems we've identified and are working on, then
check out the LMP web page (http://linux.dialnet.net/LMP).
----------------------------------
E-Mail: Doug Ledford <dledford@dialnet.net>
Date: 02-Dec-97
Time: 17:20:39
----------------------------------