mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Joachim Deguara" <joachim.deguara@amd.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: "Drift@tihlde" <drift@tihlde.org>, linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception on Opteron 265
Date: Mon, 16 Apr 2007 08:31:48 +0200	[thread overview]
Message-ID: <200704160831.48974.joachim.deguara@amd.com> (raw)
In-Reply-To: <4620F5B0.6050704@shaw.ca>

On Saturday 14 April 2007 17:39:28 Robert Hancock wrote:
> Espen Fjellvær Olsen wrote:
> > As far as we know there wasnt any unuasal activity on the server at the
> > time.
> > We updated glibc yesterday, but that shouldnt really cause such a
> > problem. So now we wonder if this might be an MCE bug, or really a HW
> > problem, and if it is one of the CPUs, or the RAM thats faulty.
> > We are running 2.6.18.
>
> Sounds like some bad RAM..

Clearly.  I would run memtest-86+[1] for a night and you should see the bad 
DIMM.  You can try the new feature in version 1.70 of that tool to display 
the DMI name of the DIMM to attempt to locate the exact DIMM.  That option is 
under Error Reporting menu.

-Joachim

[1] http://memtest.org/



  reply	other threads:[~2007-04-16  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.bATEBhtZlyN0K1NKutzIYJJSRC0@ifi.uio.no>
2007-04-14 15:39 ` Robert Hancock
2007-04-16  6:31   ` Joachim Deguara [this message]
2007-04-14 14:58 Espen Fjellvær Olsen
2007-04-17 13:56 ` Alan Cox
2007-04-17 13:57   ` Matthew Garrett
2007-04-17 14:18   ` Espen Fjellvær Olsen

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=200704160831.48974.joachim.deguara@amd.com \
    --to=joachim.deguara@amd.com \
    --cc=drift@tihlde.org \
    --cc=hancockr@shaw.ca \
    --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

Powered by JetHome