All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: [x86_64] how worried should I be about MCEs?
Date: Sat, 30 Apr 2005 13:16:49 -0700	[thread overview]
Message-ID: <4273E7B1.6020500@myrealbox.com> (raw)

Every now and then, after rebooting, the kernel notices some MCEs. 
Should I be worried about this?

(mcelog attached)

Thanks,
Andy


MCE 0
CPU 0 0 data cache from boot or resume
ADDR 480b0c84df48
   Data cache ECC error (syndrome c8)
        bit46 = corrected ecc error
        bit57 = processor context corrupt
        bit61 = error uncorrected
        bit62 = error overflow (multiple errors)
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)
STATUS ffe4681bd0e45d81 MCGSTATUS 0
MCE 2
CPU 0 3 load/store unit from boot or resume
MISC 8005003b8005003b
        bit57 = processor context corrupt
        bit59 = misc error valid
        bit61 = error uncorrected
        bit62 = error overflow (multiple errors)
STATUS fa0000000000d0c5 MCGSTATUS 0
MCE 3
CPU 0 4 northbridge from boot or resume
ADDR 102000020
   Northbridge ECC error
   ECC syndrome = 0
        bit32 = err cpu0
        bit33 = err cpu1
        bit40 = error found by scrub
        bit45 = uncorrected ecc error
        bit57 = processor context corrupt
        bit61 = error uncorrected
STATUS b600215300001e0f MCGSTATUS 0

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 20:16 Andy Lutomirski [this message]
2005-04-30 20:37 ` [x86_64] how worried should I be about MCEs? bert hubert
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=4273E7B1.6020500@myrealbox.com \
    --to=luto@myrealbox.com \
    --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 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.