mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Handle X" <xhandle@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: "Vikas Kedia" <kedia.vikas@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Can we ignore errors in mcelog if the server is running fine
Date: Fri, 28 Jul 2006 11:13:48 -0700	[thread overview]
Message-ID: <6de39a910607281113hb657981jce19f15806e82104@mail.gmail.com> (raw)
In-Reply-To: <44C9CC21.9040609@shaw.ca>

> > [root@turyxsrv ~]# mcelog
> > MCE 0
> > HARDWARE ERROR. This is *NOT* a software problem!
> > Please contact your hardware vendor
> > CPU 1 4 northbridge TSC 89a560bb249
> > ADDR 1dfa49690
> >  Northbridge Chipkill ECC error
> >  Chipkill ECC syndrome = 2021
> >       bit46 = corrected ecc error
> >  bus error 'local node response, request didn't time out
> >      generic read mem transaction
> >      memory access, level generic'
> > STATUS 9410c00020080a13 MCGSTATUS 0
>
> > Repeats whenever I do any kind of operations...
> > How severe is ChipKill errors? Should I consider throwing away CPU 1
> > and get another one.
>
> That sounds to me more like some of the RAM attached to CPU1 is bad..
I took out CPU1. Errors went away. But so is half of the RAM
(accessible only to CPU1)
Okay, I would test with swapping the RAM of CPU0 to CPU1 and test. If
I get messages again, I would change the RAM.

Thanks.
Om.

  reply	other threads:[~2006-07-28 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.5uWgnVpIOBN4Pb1aWwNzF8P2OA0@ifi.uio.no>
     [not found] ` <fa.9M8mPetEI5HZ8L2RMGPhKPm3gJA@ifi.uio.no>
2006-07-28  8:34   ` Robert Hancock
2006-07-28 18:13     ` Handle X [this message]
     [not found] <fa.2RkKSvRvPsGNSGCsUHQ9gQ8qlrg@ifi.uio.no>
2006-07-27 19:34 ` Robert Hancock
2006-07-28  5:28   ` Handle X
     [not found] <6Dc4C-1tt-47@gated-at.bofh.it>
2006-07-27 12:34 ` Bodo Eggert
2006-07-27 11:11 Vikas Kedia

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=6de39a910607281113hb657981jce19f15806e82104@mail.gmail.com \
    --to=xhandle@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=kedia.vikas@gmail.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
all inboxes | Powered by JetHome®