"D. Olson" wrote: > > CPU 1: Machine Check Exception > Bank 0: b200008000000800 > Bank 1: c200000000080a01 > Kernel Panic: CPU context corrupt > In interrupt handler - not syncing > > Alan Cox had this to say on the matter: > > "If your cpu context corrupt is with a machine check exception report then > your processor took an internal fault reporting trap. So its not a happy > bit of silicon I suspect - be it overclocked, overheated, or even faulty." > > Now, the trouble is, it is a dual PII 333MHz system, and I don't overclock it > and it has been working fine before this for a few months. It's uptime was > around 30 days when this happened. > > What is the cause of it? Just too much heat? It seems weird that it would > happen right now... I know people who have servers that run forever without > this kind of problem... >
Think of this occurrence like a light bulb going dead: for hundreds of hours it work just fine, and then in a single nanosec it is gone. It may be that your cpu just "gave up the ghost". Since you are not overclocking, you could check for high temp. Some things to do would be to install a new "super" fan on cpu and/or open case to put a fan pointing directly at the cpu socket. And, because you are running dual cpu's, you might play with taking one out and try each cpu separately to glean results. Good luck, drjung -- J. Craig Woods UNIX/NT Network/System Administration http://www.trismegistus.net/resume.html Character is built upon the debris of despair --Emerson
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
