mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [x86_64] how worried should I be about MCEs?
Date: Sat, 30 Apr 2005 22:37:23 +0200	[thread overview]
Message-ID: <20050430203723.GA8122@outpost.ds9a.nl> (raw)
In-Reply-To: <4273E7B1.6020500@myrealbox.com>

On Sat, Apr 30, 2005 at 01:16:49PM -0700, Andy Lutomirski wrote:
> Every now and then, after rebooting, the kernel notices some MCEs. 
> Should I be worried about this?

If these reports are true, they would be worrying. But I find them a bit
hard to believe - the bit combinations don't appear to make sense.

I have an AMD64 machine which logs 'MCE reported' every once in a while but
otherwise functions perfectly and I haven't yet coaxed it into telling me
the content of the errors.

Might there be a bug here? How did you create this log?

> STATUS f66440000000438d MCGSTATUS 0
> MCE 1
> CPU 0 1 instruction cache from boot or resume
> ADDR 75e2bb87ec57f8e0
>   Instruction cache ECC error
>        bit32 = err cpu0
>        bit33 = err cpu1
>        bit35 = res3
>        bit43 = res11
>        bit45 = uncorrected ecc error
>        bit46 = corrected ecc error
>        bit55 = res23
>        bit56 = res24
>        bit57 = processor context corrupt
>        bit59 = misc error valid
>        bit61 = error uncorrected
>        bit62 = error overflow (multiple errors)

This would be one hell of an error - both corrected and uncorrected.

Regards,

bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services

  reply	other threads:[~2005-04-30 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 20:16 Andy Lutomirski
2005-04-30 20:37 ` bert hubert [this message]
2005-04-30 21:02   ` Andy Lutomirski
2005-04-30 21:41     ` possibly bogus AMD64 MCE reporting bert hubert
2005-05-02 16:49 ` [x86_64] how worried should I be about MCEs? 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=20050430203723.GA8122@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@myrealbox.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

all inboxes | Powered by JetHome®