MCA messages after upgrade to 8.2-BEAT1

Alan Cox alan.l.cox at gmail.com
Sat Dec 25 00:03:57 UTC 2010


On Fri, Dec 24, 2010 at 5:08 PM, Carl Johnson <carlj at peak.org> wrote:

> Alan Cox <alan.l.cox at gmail.com> writes:
>
> > 2010/12/23 Dan Langille <dan at langille.org>
> >
> >> On 12/22/2010 9:57 AM, John Baldwin wrote:
> >>
> >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote:
> >>>
> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e400000000833
> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0000000000000105,
> >>>> Status 0x0000000000000000
> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33,
> >>>> APIC ID 0
> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD
> >>>> Memory
> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0
> >>>>
> >>>
> >>> You are getting corrected ECC errors in your RAM.  You see them once an
> >>> hour
> >>> because we poll the machine check registers once an hour.  If this
> happens
> >>> constantly you might have a DIMM that is dying?
> >>>
> >>
> >> John:
> >>
> >> I take it these ECC errors *may* have been happening for some time. What
> >> has changed is the OS now polls for the errors and reports them.
> >>
> >>
> > Yes, we enabled MCA by default in 8.1-RELEASE.
>
> Is there some reason that it is only available for i386 and not for
> amd64?  Linux has something called mcelog, for machine check errors,
> which sounds similar and is available for amd64.
>
>
Perhaps I'm misunderstanding your question, but our MCA driver is supported
and enabled by default on both i386 and amd64.

Alan


More information about the freebsd-stable mailing list