Alan Cox enscribed thusly:
> > I'm running kernel 2.1.127 on my users server and have been running
> > into some problems. It's ok for about 13 hours and then it locks up and
> > my software watchdog reboots it (at least i think that's what happens...
> > The machine is a Dual PPro 180 overclocked to 199.5 but the kernel is UP
> Your report is worthless. Stop overclocking and see if you can reproduce it
His report may be useless, but we've got a BUNCH of people on 4
or 5 different threads all chiming in with basically the same problem.
Everyone who has gotten back to me has reported that they have built with
SMP disabled in the makefile. This thing has been plaguing me since
2.1.127pre7 when I could finally build with SMP commented out (2.1.127pre3
would segfault gcc in sched.c). I've been playing process of elimination
since then and have gotten real suspicious of a problem somewhere in the
schedular or related areas on SMP disabled builds. An SMP enabled build
on a uniprocessor has now been up for over 11 hours. My failures were
occuring between 2 hours and 22 hours, so it's still WAY too early too
tell if it really is the uniprocessor build. But something IS messed up.
Any thoughts on any way we can isolate this animal better?
> Alan
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/