public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: machine check errors
Date: Thu, 12 Jan 2006 22:37:39 -0600	[thread overview]
Message-ID: <43C72E93.1030602@shaw.ca> (raw)
In-Reply-To: <5ukd5-3kf-17@gated-at.bofh.it>

don fisher wrote:
> I have a Tyan S2892 board with a pair Opteron 288 dual core cpus and 
> 16GB dram. I receive the errors shown in the attached file, mcelog. It 
> appears that these occur when the free memory becomes small, there is a 
> lot in the cache, and a lot of IO.
> 
> The Tyan S2892 has an Nvidia Crush K8-04, which I think they call the 
> southbridge. My errors appear to be related to the north bridge. There 
> is an AMD 8131 PCI-X controller that runs the PCI slots. There is a 
> 3WARE 9500-12 located in one of the PCI-X slots.
> 
> I have run Memtest86+-1.65 for 24 hours without errors. I recently 
> upgraded the BIOS to V2.00 without any remarkable changes.
> 
> I am running 2.6.15 within a current Fedora Core4 configuration.
> 
> I would appreciate any advice as to how to proceed. I have not noticed 
> any adverse behavior from the mce's. But that could be masked is data 
> transfered or ???.
> 
> Could there be any connection with the memory cache? Thanks in advance 
> for your assistance.

I would say you likely do have some bad RAM, that seems to be what those 
MCEs are indicating. Depending on the configuration, Memtest86 may not 
find all the errors if they are being corrected by ECC..

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


       reply	other threads:[~2006-01-13  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5ukd5-3kf-17@gated-at.bofh.it>
2006-01-13  4:37 ` Robert Hancock [this message]
2006-01-12 23:37 machine check errors don fisher
2006-01-13 10:10 ` Alan Cox
2006-01-13 15:31 ` Roger Heflin
2006-01-14  0:28   ` Doug Thompson

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=43C72E93.1030602@shaw.ca \
    --to=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