Re: kernel: MCA: CPU 0 COR (1) internal parity error

On Fri, 16 Jan 2015 20:45:39 +0100 Matthias Apitz <guru_at_unixarea.de> wrote

> Hello,
> 
> I'm running since some days a recent -HEAD r276659 on an Acer C720
> Chromebook which works very nicely and fast (I really have never seen
> such a fast KDE4 desktop).
> 
> >From time to time (let's say 2-3 times a day) I see messages like this
> in /var/log/messages:
> 
> Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x90000040000f0005
> Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0000000000000c07,
> Status 0x0000000000000000 Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor
> "GenuineIntel", ID 0x40651, APIC ID 0 Jan 16 12:04:24 c720-r276659 kernel:
> MCA: CPU 0 COR (1) internal parity error 
>
> the kernel is:
> 
> # uname -a
> FreeBSD c720-r276659 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r276659M: Tue Jan 
> 6 12:55:25 CET 2015
> guru_at_vm-poudriere-r269739:/usr/local/acerC720/obj/usr/local/acerC720/src/sys/
> GENERIC i386 
>
> i.e. the i386 version (because I compile everything in a VM)
> 
> Are the above messages really a hardware problem?
Last time I saw this, it was cache on one of the CPU's going south (bad).

My experience, anyway.

--Chris
> 
> Thanks
> 
>     matthias
> 
> -- 
> Matthias Apitz, guru_at_unixarea.de, http://www.unixarea.de/ +49-170-4527211
> 1989-2014: The Wall was torn down so that we go to war together again.
> El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez.
> Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"