linux-kernel - Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?

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]

Date:	Mon, 08 Dec 2008 10:56:08 +0100
From:	Andi Kleen <ak@...ux.intel.com>
To:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
CC:	Giangiacomo Mariotti <gg.mariotti@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org
Subject: Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?


> IIRC, this error is not what happen on the time [301.7320xx] during
> boot, but happen before the boot.  Since the record says "Processor
> context corrupt," MCE handler should call panic(or do something stop
> the system) if the context actually corrupted during the boot.

The weird thing is that 301 seconds is quite a long delay for that.
It should happen  relatively quickly at boot as the CPUs are initialized.

> 
> In other words, it seems that 1) the error was recorded at last time
> when your machine crashed unexpectedly(by cosmic-ray etc.) and not cleared
> yet, or 2) your machine is doing something wrong in every reset/poweroff.

When it happens consistently at each boot then yes it's likely something
leaking from the BIOS initialization sequence. Perhaps try a BIOS update?

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