linux-kernel - Re: MCE hardware error, but no message

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: <4D7EC069.6060404@jp.fujitsu.com>
Date:	Tue, 15 Mar 2011 10:27:05 +0900
From:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
To:	Jan Engelhardt <jengelh@...ozas.de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	x86@...nel.org
Subject: Re: MCE hardware error, but no message

(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

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