linux-kernel - Re: How to interpret MCE messages?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1163003354.23956.43.camel@localhost.localdomain>
Date:	Wed, 08 Nov 2006 16:29:13 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	martin f krafft <madduck@...duck.net>
Cc:	linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: How to interpret MCE messages?

Ar Mer, 2006-11-08 am 17:20 +0100, ysgrifennodd martin f krafft:
> Thanks to mcelog, I am now regularly seeing messages like this on an
> amd64 machine:
> 
>   kernel: Machine check events logged
>         bit46 = corrected ecc error
>     Data cache ECC error (syndrome 5b)

Cache.. not memory

>     memory/cache error 'data read mem transaction, data transaction, level 2'

L2 Cache

> Before I go out and buy a new motherboard (as I assume that it's
> a L1/L2 cache problem), 

L1/L2 cache are on the CPU these days. Double check with the processor
docs and vendor but I think mcelog is actually trying to tell you that
the CPU wants to be warranty returned. It might also of course be a heat
problem.

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