CPU failures ... or something else ?

So you are saying, that yes, it _is_ possible that my equipment is not faulty in any way ?

thanks!

Quoted 52 lines · Bubba

try turning off the Machine Check Exception in the kernel as it is just buggy on some machines, not necessarily a bug in the kernel, or without recompiling, use the kernel param "nomce"

Quoted 33 lines · Josh Brooks

Hello,

I have a dual p3 866 running 2.4 kernel that is crashing once every few days leaving this on the console:

Message from syslogd@localhost at Tue Dec 24 11:30:31 2002 ... localhost kernel: CPU 1: Machine Check Exception: 0000000000000004

Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ... localhost kernel: Bank 4: b200000000040151

Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ... localhost kernel: Kernel panic: CPU context corrupt

Word on the street is that this indicates hardware failure of some kind (cpu, bus, or memory). My main question is, is that very surely the culprit, or is it also possible that all of the hardware is perfect and that a bug in the kernel code or some outside influence (remote exploit) is causing this crash ?

Basically, I am ordering all new hardware to swap out, and I just want to know if there is some remote possibility that my hardware is actually just fine and this is some kind of software error ?

ALSO, I have not been physically at the console when this has happened, and have not tried this yet, but whatever that thing is where you press ctrl-alt-printscreen and get to enter those post-crash commands - do you think that would work in this situation, or does the above error hard lock the system so you can't do those emergency measures ?

Quoted 8 lines

thanks!

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

I never said that. A bad CPU would be my last guess. My first two are buggy board (use nomce) or bad addresses in your ram. try running Memtest86
(http://www.memtest86.com) for a few minutes and see if you get any errors.

Quoted 58 lines · you

So you are saying, that yes, it _is_ possible that my equipment is not faulty in any way ?

thanks!

Quoted 52 lines · Bubba

try turning off the Machine Check Exception in the kernel as it is just buggy on some machines, not necessarily a bug in the kernel, or without recompiling, use the kernel param "nomce"

Quoted 33 lines · Josh Brooks

Hello,

I have a dual p3 866 running 2.4 kernel that is crashing once every few days leaving this on the console:

Message from syslogd@localhost at Tue Dec 24 11:30:31 2002 ... localhost kernel: CPU 1: Machine Check Exception: 0000000000000004

Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ... localhost kernel: Bank 4: b200000000040151

Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ... localhost kernel: Kernel panic: CPU context corrupt

Word on the street is that this indicates hardware failure of some kind (cpu, bus, or memory). My main question is, is that very surely the culprit, or is it also possible that all of the hardware is perfect and that a bug in the kernel code or some outside influence (remote exploit) is causing this crash ?

Basically, I am ordering all new hardware to swap out, and I just want to know if there is some remote possibility that my hardware is actually just fine and this is some kind of software error ?

ALSO, I have not been physically at the console when this has happened, and have not tried this yet, but whatever that thing is where you press ctrl-alt-printscreen and get to enter those post-crash commands - do you think that would work in this situation, or does the above error hard lock the system so you can't do those emergency measures ?

Quoted 8 lines

thanks!

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

I thought it was significant that I am running 2.4.1 on _identical_ hardware without problems - presumably if that is the case then running 2.4.16 on the same hardware should be fine as well (in terms of a buggy board) - therefore I suspect bad hardware.

Is this good reasoning?