From: Andi Kleen <ak@linux.intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?
Date: Mon, 08 Dec 2008 10:56:08 +0100 [thread overview]
Message-ID: <493CEF38.3060004@linux.intel.com> (raw)
In-Reply-To: <493CEAA0.50201@jp.fujitsu.com>
> 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
next prev parent reply other threads:[~2008-12-08 9:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:21 [HW PROBLEM] Intel I7 MCE. Erratum or not? Giangiacomo Mariotti
2008-12-06 20:58 ` Robert Hancock
2008-12-06 21:43 ` Giangiacomo Mariotti
2008-12-06 21:47 ` Robert Hancock
2008-12-06 22:16 ` Giangiacomo Mariotti
2008-12-07 3:25 ` Robert Hancock
2008-12-07 3:42 ` Giangiacomo Mariotti
2008-12-07 21:55 ` Giangiacomo Mariotti
2008-12-07 22:13 ` Arjan van de Ven
2008-12-07 23:21 ` Giangiacomo Mariotti
2008-12-08 6:48 ` Giangiacomo Mariotti
2008-12-08 7:42 ` Hidetoshi Seto
2008-12-08 8:04 ` Giangiacomo Mariotti
2008-12-08 9:36 ` Hidetoshi Seto
2008-12-08 9:56 ` Andi Kleen [this message]
2008-12-08 10:02 ` Eric Dumazet
2008-12-08 10:18 ` Andi Kleen
2008-12-08 10:26 ` Hidetoshi Seto
2008-12-08 10:53 ` Giangiacomo Mariotti
2008-12-08 11:10 ` Hidetoshi Seto
2008-12-08 11:16 ` Giangiacomo Mariotti
2008-12-08 12:04 ` Andi Kleen
2008-12-08 12:37 ` Giangiacomo Mariotti
2008-12-09 5:54 ` Giangiacomo Mariotti
2008-12-09 11:31 ` Andi Kleen
2008-12-09 11:57 ` Giangiacomo Mariotti
2008-12-15 20:59 ` Giangiacomo Mariotti
[not found] ` <alpine.DEB.1.10.0812081314010.18782@uplift.swm.pp.se>
[not found] ` <493D296B.1080205@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812081724080.18782@uplift.swm.pp.se>
[not found] ` <493D6FB4.9090909@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812082145410.18782@uplift.swm.pp.se>
[not found] ` <12bfabe40812082146r3ea000em7a8f725101a50bd5@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090737410.18782@uplift.swm.pp.se>
2008-12-09 7:37 ` OFFLIST " Giangiacomo Mariotti
[not found] ` <12bfabe40812082319x4ed6c9m5b744e51cdd3d838@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090857590.18782@uplift.swm.pp.se>
2008-12-09 8:30 ` Giangiacomo Mariotti
2008-12-09 8:34 ` Giangiacomo Mariotti
2008-12-08 10:26 ` Giangiacomo Mariotti
2008-12-08 10:57 ` Hidetoshi Seto
2008-12-08 11:14 ` Giangiacomo Mariotti
2008-12-06 22:37 ` Giangiacomo Mariotti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493CEF38.3060004@linux.intel.com \
--to=ak@linux.intel.com \
--cc=arjan@infradead.org \
--cc=gg.mariotti@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox