linux-kernel - Re: MCE going wild, 14 megs of this in the logs

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: <Pine.LNX.4.64.0803310148540.32241@twin.jikos.cz>
Date:	Mon, 31 Mar 2008 01:49:54 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Gene Heskett <gene.heskett@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: MCE going wild, 14 megs of this in the logs

On Sun, 30 Mar 2008, Gene Heskett wrote:

> Mar 30 16:46:42 coyote kernel: [469249.031832] MCE: The hardware reports a non 
> fatal, correctable incident occurred on CPU 0.
> Mar 30 16:46:42 coyote kernel: [469249.031838] Bank 1: d400400000000152
> Mar 30 16:46:42 coyote kernel: [469249.031841] MCE: The hardware reports a non 
> fatal, correctable incident occurred on CPU 0.
> Mar 30 16:46:42 coyote kernel: [469249.031844] Bank 2: d40040000000017a
> Its always the same 2 addresses reported, and every 15 seconds.  So I have the 
> non-fatal part of MCE now turned off, & 2.6.24.4 rebuilding.

Hi,

you possible have some buggy hardware. I'd suggest running this through 
mcelog, which should decode the MCE reason.

-- 
Jiri Kosina
SUSE Labs

--
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/