Re: Processor context corrupt.
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: Re: Processor context corrupt.
- From: Marc Aymerich <email@example.com>
- Date: Wed, 4 Jan 2012 22:18:01 +0100
- Message-id: <[🔎] CA+DCN_sUz18BAQ6Hv9vrMP5gKjoPRcKsHqaJ_yS3zar3uS1c0w@mail.gmail.com>
- In-reply-to: <CA+DCN_uLMm-T-UAHXaYtys5gzmrjS2NVBdriFARJckyRv1yupg@mail.gmail.com>
- References: <CA+DCN_sr0CFcySvtezS=xHrXr7DmBVfBwid8dU_cASpwqN+aRQ@mail.gmail.com> <9683B1F7-DCC2-4CE8-A1AA-B9B5C7D49CC5@gmail.com> <CA+DCN_tOAaLvvr9y14B9U8HzbhO5tTknx=tj9vCWn4+JYn6+UQ@mail.gmail.com> <firstname.lastname@example.org> <4EF38A6F.email@example.com> <firstname.lastname@example.org> <CA+DCN_uLMm-T-UAHXaYtys5gzmrjS2NVBdriFARJckyRv1yupg@mail.gmail.com>
On Fri, Dec 23, 2011 at 7:49 PM, Marc Aymerich <email@example.com> wrote:
> On Thu, Dec 22, 2011 at 11:44 PM, Sven Hartge <firstname.lastname@example.org> wrote:
>> Robert L Mathews <email@example.com> wrote:
>>> Sven Hartge wrote:
>>>> In all my cases of a MCE in the past, this was _always_ caused by
>>>> faulty hardware, split roghly 50:50 between broken mainboard or
>>>> broken CPU.
>>> As another data point, I recently saw a repeatable MCE error on a
>>> machine with faulty memory during a new hardware burn-in test.
>>> Replacing the memory fixed it.
>> Might happen with the newer CPUs with integrated memory controller.
> Thank you all for your help :)
> Yesterday we decide to remove two memory sims, since these two sims
> have been plugged into the server just few months ago, during a
> general memory upgrade. Hope that there is no mceing anymore :)
two weeks have passed without see any context corrupt. Seems that it
was a memory problem after all. Thank you guys!