Hi Juhan,
> After searching the archives of the list I found some similar reports
> from September and December 2000 but as far as I understood
> the cause of
> the error was blamed on the CPU. Is this the most probable case?
>
> Best regards,
>
> Juhan Ernits
>
> -- /var/log/kern.log
>
> May 6 06:47:25 market kernel: CPU 0: Machine Check
> Exception: 0000000000000004
> May 6 06:47:25 market kernel: Bank 4: b200000000040151<0>Kernel
> panic: CPU context corrupt
Yes. consensus of the messages I received is that it's the cpu flagging an
internal hardware problem.
Suggested causes include:
overclocking
thermal problems
CPU actually bad
Definitely not caused by:
Bad Rams, mb-chipset.
In my case the error only occured once and never again - marked it up to bad
karma on that day.
Bye, Martin
-
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/
