mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: How to interpret MCE messages?
Date: Wed, 8 Nov 2006 17:20:22 +0100	[thread overview]
Message-ID: <20061108162022.GA4258@piper.madduck.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

Thanks to mcelog, I am now regularly seeing messages like this on an
amd64 machine:

  kernel: Machine check events logged
        bit46 = corrected ecc error
    Data cache ECC error (syndrome 5b)
    memory/cache error 'data read mem transaction, data transaction, level 2'
  ADDR 38ed9200
  CPU 0 0 data cache TSC fe4f9128ade
  MCE 0
  STATUS 942dc00000000136 MCGSTATUS 0

The RAM modules are *not* ECC modules, nor does the Asus K8V Deluxe
motherboard support ECC to my knowledge. I've turned ECC support on
and off in the Bios without any effect.

I've already run memtest86+ for hours without finding any problems,
and I've removed each of the two memory modules for a while, but
I still saw these errors appearing.

Before I go out and buy a new motherboard (as I assume that it's
a L1/L2 cache problem), I'd like to know how I am to interpret these
MCE dumps and how I could use them to actually pinpoint the source
of the problem.

Cheers,

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
spamtraps: madduck.bogus@madduck.net
 
"america may be unique in being a country which has leapt
 from barbarism to decadence without touching civilization."
                                                        -- john o'hara

[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-11-08 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:20 martin f krafft [this message]
2006-11-08 16:29 ` Alan Cox
2006-11-08 23:12   ` martin f krafft
2006-11-15  9:27   ` martin f krafft
2006-11-17 23:27     ` dean gaudet
2006-11-09  4:11 ` Valdis.Kletnieks
2006-11-11  4:31   ` Mark Rosenstand

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=20061108162022.GA4258@piper.madduck.net \
    --to=madduck@madduck.net \
    --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®