linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Stumpf <mjstumpf@pobox.com>
To: linux-raid@vger.kernel.org
Subject: random lockups, raid problems SOLVED (plus a question)
Date: Tue, 06 Dec 2005 14:19:37 -0600	[thread overview]
Message-ID: <4395F259.1080801@pobox.com> (raw)

Sure it's a FAQ.  It's probably even documented.  And, I know it, but it 
still surprised me.  Such is life:

2/3 sticks of perfectly good ECC ram in an old server class p3 board 
apparently have gone bad.  Result?  Random lockups/reboots with nothing 
in the system logs to even lend a clue.

Memtest86 showed one problem immediately, and after some time, exposed 
some more.  Remove the bad memory and it works fine.

Is there some daemon that can more actively monitor memory function?  I 
must have had this problem for months, but with sputtering hard drives 
that were slowly dying and causing very similar problems, this diagnosis 
got muddled.

Regards-
Michael Stumpf





             reply	other threads:[~2005-12-06 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 20:19 Michael Stumpf [this message]
2005-12-07  7:49 ` random lockups, raid problems SOLVED (plus a question) Mattias Wadenstein

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=4395F259.1080801@pobox.com \
    --to=mjstumpf@pobox.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).