From: Andi Kleen <andi@firstfloor.org>
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: Wed, 16 Mar 2011 11:31:38 -0700 [thread overview]
Message-ID: <m2tyf2lxx1.fsf@firstfloor.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1103122136220.20070@obet.zrqbmnf.qr> (Jan Engelhardt's message of "Sat, 12 Mar 2011 21:49:19 +0100 (CET)")
Jan Engelhardt <jengelh@medozas.de> writes:
> 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.
mcelog logs them. The kernel shouldn't be spewing these messages
at all, especially not for corrected errors (this is a still
unfixed regression for Intel CPUs)
Here's an older fix:
http://git.kernel.org/?p=linux/kernel/git/ak/linux-mce-2.6.git;a=commit;h=6e3c7411d2b86bff210c59caa432e8e862037bfd
> How would I get the messages to run through mcelog?
They are already logged, no need to do anything further.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2011-03-16 18:32 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
2011-03-16 18:31 ` Andi Kleen [this message]
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=m2tyf2lxx1.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.