From: Orion Poplawski <orion@cora.nwra.com>
To: linux-kernel@vger.kernel.org
Subject: Re: EDAC chipkill messages
Date: Fri, 19 Jan 2007 09:45:43 -0700 [thread overview]
Message-ID: <45B0F5B7.4080703@cora.nwra.com> (raw)
In-Reply-To: <45B00CD7.8050802@shaw.ca>
Robert Hancock wrote:
> Orion Poplawski wrote:
>> Can someone please explain to me what these mean?
>>
>> EDAC k8 MC1: general bus error: participating processor(local node
>> origin), time-out(no timeout) memory transaction type(generic read),
>> mem or i/o(mem access), cache level(generic)
>> EDAC MC1: CE page 0xfbf6f, offset 0x4d0, grain 8, syndrome 0xc8f4, row
>> 1, channel 0, label "": k8_edac
>> EDAC MC1: CE - no information available: k8_edac Error Overflow set
>> EDAC k8 MC1: extended error code: ECC chipkill x4 error
>>
>> Thanks!
>>
>
> Sounds like you're having some memory ECC errors.. some Memtest86, etc.
> runs may be in order. You may be able to figure out from this info what
> DIMM is having the problem.
>
That was my assumption as well, but was hoping someone could decode the
above information and point me to the problem chip. I ran Memtest86
overnight but found no problems, but don't know if it needs to run in a
particular ECC mode.
This is a dual proc 275 system with 4 1GB DIMMs. Guessing that MC1 is
the controller on the second CPU. Would row 1 be the second DIMM?
next prev parent reply other threads:[~2007-01-19 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.CZkzgccjpiJW6cRrbtRvg/+4HMg@ifi.uio.no>
2007-01-19 0:12 ` EDAC chipkill messages Robert Hancock
2007-01-19 16:45 ` Orion Poplawski [this message]
2007-01-19 19:34 ` Doug Thompson
2007-01-18 22:55 Orion Poplawski
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=45B0F5B7.4080703@cora.nwra.com \
--to=orion@cora.nwra.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox