All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: thockin@hockin.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: mcelog ?
Date: Tue, 16 May 2006 11:37:00 +0200	[thread overview]
Message-ID: <20060516113700.15733892.skraw@ithnet.com> (raw)
In-Reply-To: <20060515152008.GA25367@hockin.org>

On Mon, 15 May 2006 08:20:08 -0700
thockin@hockin.org wrote:

> On Mon, May 15, 2006 at 11:42:43AM +0200, Stephan von Krawczynski wrote:
> > HARDWARE ERROR
> > CPU 1: Machine Check Exception:                4 Bank 4: b60a200170080813
> > TSC 89cfb4725b17 ADDR 1025cb3f0 
> > This is not a software problem!
> > Run through mcelog --ascii to decode and contact your hardware vendor
> > Kernel panic - not syncing: Machine check
> > 
> > Of course I ran mcelog but I don't quite understand how the additional info
> > helps me finding the problem.
> > Is this a problem with RAM? And if, which one?
> 
> It sounds like a memory error, but there are some other bank4 errors that
> can crop up.  What does mcedecode say?

Well, here it is:

HARDWARE ERROR
CPU 1 4 northbridge TSC 89cfb4725b17 
  Northbridge Chipkill ECC error
  Chipkill ECC syndrome = 7014
       bit32 = err cpu0
       bit45 = uncorrected ecc error
       bit57 = processor context corrupt
       bit61 = error uncorrected
  bus error 'local node origin, request didn't time out
      generic read mem transaction
      memory access, level generic'
STATUS b60a200170080813 MCGSTATUS 4
This is not a software problem!

 
Is this some sort of mem error?

Thank you for your help
-- 
Regards,
Stephan

  reply	other threads:[~2006-05-16  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15  9:42 mcelog ? Stephan von Krawczynski
2006-05-15 15:20 ` thockin
2006-05-16  9:37   ` Stephan von Krawczynski [this message]
2006-05-15 15:45 ` Andi Kleen
2006-05-20 22:46 ` Bernd Pfrommer

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=20060516113700.15733892.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@hockin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.