From: Andi Kleen <ak@suse.de>
To: Evgeny Rodichev <er@sai.msu.su>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 mce_log question
Date: 05 Nov 2005 18:35:53 +0100 [thread overview]
Message-ID: <p73k6fn2e12.fsf@verdi.suse.de> (raw)
In-Reply-To: <Pine.GSO.4.63.0511021822010.28234@ra.sai.msu.su>
Evgeny Rodichev <er@sai.msu.su> writes:
> Hello,
>
> at Opteron-based x86_64 system sometimes I get message
>
> Machine check events logged
>
> (non-fatal). How can I read the correspondent events?
Read the help
config X86_MCE
bool "Machine check support" if EMBEDDED
default y
help
Include a machine check error handler to report hardware errors.
This version will require the mcelog utility to decode some
machine check error logs. See
ftp://ftp.x86-64.org/pub/linux/tools/mcelog
> From the source
> code (arch/x86_64/kernel/mce.c) it sounds like some misc device with
> MISC_MCELOG_MINOR 227 is registered (with name "mcelog"?), but there is
> no such device under /dev.
Your distribution is broken then. In fact it is supposed to run
mcelog regularly from a cronjob to log machine check events into
a disk log. Complain to them.
-Andi
prev parent reply other threads:[~2005-11-05 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 15:32 Evgeny Rodichev
2005-11-05 17:35 ` 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=p73k6fn2e12.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=er@sai.msu.su \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®