mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Vikas Kedia <kedia.vikas@gmail.com>
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel panic at load average of 24 is it acceptable ?
Date: Mon, 17 Jul 2006 08:28:03 -0600	[thread overview]
Message-ID: <44BB9E73.50704@shaw.ca> (raw)
In-Reply-To: <fa.pLqL2zHzVigenRd4nxSUVosmfvk@ifi.uio.no>

Vikas Kedia wrote:
> Here is the output of mcelog:
> root@srv1:~# less /var/log/mcelog
> MCE 0
> CPU 0 0 data cache TSC 6988ae18046
> ADDR f87f5ec0
>  Data cache ECC error (syndrome ce)
>       bit46 = corrected ecc error
>  bus error 'local node origin, request didn't time out
>      data read mem transaction
>      memory access, level generic'
> STATUS 9467400000000833 MCGSTATUS 0
> MCE 0
> CPU 0 0 data cache TSC 723b38a3633
> ADDR 3d9fc0
>  Data cache ECC error (syndrome ce)
>       bit46 = corrected ecc error
>       bit62 = error overflow (multiple errors)
>  bus error 'local node origin, request didn't time out
>      data read mem transaction
>      memory access, level generic'
> STATUS d467400000000833 MCGSTATUS 0
> 
> Since it shows ECC error is the hypothesis correct that its the RAM
> problem and replacing it should solve the problem.

That looks like a data cache ECC error, which would point to a CPU 
problem in that case..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-07-17 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.GOIim+nD/em++2ZW3u6yf9zZzH8@ifi.uio.no>
     [not found] ` <fa.pLqL2zHzVigenRd4nxSUVosmfvk@ifi.uio.no>
2006-07-17 14:28   ` Robert Hancock [this message]
2006-07-17 14:47     ` Andreas Mohr
2006-07-17  7:08 Vikas Kedia
2006-07-17  7:24 ` Andreas Mohr
2006-07-17  7:55   ` Vikas Kedia
2006-07-17 18:16     ` Andrey Borzenkov

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=44BB9E73.50704@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=andi@rhlx01.fht-esslingen.de \
    --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®