Actually now looks like just the opposite. Running an SMP kernel
on a single processor seems to work nicely. It's the UP build that is
hosed. Now have multiple confirmations. There may be timing issues,
driver issues, or interrupt issues that are causing some systems to be
more suceptable than others.
I have one system that seems to be unaffected by the 127/128 flu.
Other systems are chronic. The affected systems can be "cured" by building
an SMP kernel. So far, not one failure, experienced or reported to me by
others, with an SMP build.
> It just isn't true that this is a generic 2.1.x, x >= 125 UP problem; if it
> was, the yelling in l-k would have me stone deaf.
IMHO... It's NOT >= 125 UP... I think the problem was introduced
somewhere around 127pre3. With 127pre2 I had no evidence of this problem.
Unfortunately 127pre3 could not be compiled UP because something changed
causing gcc to segfault attempting to compile sched.c. 127pre3 worked
fine for me. 127pre7 (the next one I tested) could compile UP but exhibited
this problem. Someone else came up with the 127/128 flu label. Seems
appropriate...
Last I did a nose count, there are no less that eight subject threads
running on l-k on this very problem...
> --
> Horst von Brand vonbrand@sleipnir.valparaiso.cl
> Casilla 9G, Viņa del Mar, Chile +56 32 672616
Mike
-- Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com (The Mad Wizard) | (770) 925-8248 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/