public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Re: MCE hardware error, but no message
Date: Tue, 15 Mar 2011 10:27:05 +0900	[thread overview]
Message-ID: <4D7EC069.6060404@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1103122136220.20070@obet.zrqbmnf.qr>

(2011/03/13 5:49), Jan Engelhardt wrote:
> 
> 
> Running Linux 2.6.37, I am getting these errors on one of a box:
> 
> [696782.810387] [Hardware Error]: No human readable MCE decoding support 
> on this CPU type.
> [696782.810470] [Hardware Error]: Run the message through 'mcelog 
> --ascii' to decode.
> [696783.585853] [Hardware Error]: No human readable MCE decoding support 
> on this CPU type.
> [696783.585937] [Hardware Error]: Run the message through 'mcelog 
> --ascii' to decode.
> 
> Except that it never tells me the actual non-human readable form.
> The error starts to show after 6-48 hours after a reboot (including 
> warm reboots). A second machine of the exact same configuration shows no 
> problems over the past 30 days. Environmental sensors of the problem box 
> show normal parameters.
> 
> How would I get the messages to run through mcelog?

It looks like a kind of corrected error.

Let's try the latest mcelog:
  git://git.kernel.org/pub/scm/utils/cpu/mce/mcelog.git


Thanks,
H.Seto


  reply	other threads:[~2011-03-15  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 20:49 MCE hardware error, but no message Jan Engelhardt
2011-03-15  1:27 ` Hidetoshi Seto [this message]
2011-03-16 18:31 ` Andi Kleen

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=4D7EC069.6060404@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /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