From: martin f krafft <madduck@madduck.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: How to interpret MCE messages?
Date: Thu, 9 Nov 2006 00:12:48 +0100 [thread overview]
Message-ID: <20061108231248.GC28926@piper.madduck.net> (raw)
In-Reply-To: <1163003354.23956.43.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
also sprach Alan Cox <alan@lxorguk.ukuu.org.uk> [2006.11.08.1729 +0100]:
> > memory/cache error 'data read mem transaction, data
> > transaction, level 2'
>
> L2 Cache
Gosh, I must be blind. Somehow there was too much information in
that dump. Thanks Alan!
> > Before I go out and buy a new motherboard (as I assume that it's
> > a L1/L2 cache problem),
>
> L1/L2 cache are on the CPU these days. Double check with the processor
> docs and vendor but I think mcelog is actually trying to tell you that
> the CPU wants to be warranty returned. It might also of course be a heat
> problem.
I am afraid the CPU might be out of warranty, but I'll try; I doubt
it's a heat problem since there are plenty fans and the machine's
interior is actually of quite agreeable temperature.
I'll check the CPU. Again, thanks.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
if you find a spelling mistake in the above, you get to keep it.
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-08 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 16:20 martin f krafft
2006-11-08 16:29 ` Alan Cox
2006-11-08 23:12 ` martin f krafft [this message]
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=20061108231248.GC28926@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®