From: Alan Cox <alan@redhat.com>
To: raz@macs.hw.ac.uk (Ross Macintyre)
Cc: alan@redhat.com (Alan Cox),
linux-kernel@vger.kernel.org, linux-megaraid-devel@dell.com,
salvini@macs.hw.ac.uk, donald@macs.hw.ac.uk
Subject: Re: new raid server crashed - no idea why!
Date: Fri, 18 Jul 2003 06:49:15 -0400 (EDT) [thread overview]
Message-ID: <200307181049.h6IAnFi00440@devserv.devel.redhat.com> (raw)
In-Reply-To: <SIMEON.10307181006.C@pcraz.macs.hw.ac.uk> from "Ross Macintyre" at Gor 18, 2003 10:37:06
> > guess fro the traces and the fact the dual athlons are infamously
> > sensitive about ram
>
> Could you be a bit more specific about this please?
I have a near endless series of dual athlon bug reporta that go
It crashes randomly
Run memtest86
It says lots of bad things
In paticular if you have more than two banks of RAM on dual athlon boards it
almost always has to be registered DIMM.
> swap the memory about and run memtest86 on the problem machine's memory
> in the other machine. (I am assuming here that the machine needs to be
> shut down to run memtest86?)
Only if its another identical dual athlon and then you'd be better
running the other one and testing the one with the problem.
> to have it crashing on me, but before I test the memory, I want to have
> looked at all the other possibilities first.
> Any more suggestions?
Until you've checked the memory - not really.
prev parent reply other threads:[~2003-07-18 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 15:29 new raid server crashed - no idea why! Ross Macintyre
2003-07-16 16:01 ` Alan Cox
2003-07-18 9:37 ` Ross Macintyre
2003-07-18 10:49 ` Alan Cox [this message]
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=200307181049.h6IAnFi00440@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=donald@macs.hw.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=raz@macs.hw.ac.uk \
--cc=salvini@macs.hw.ac.uk \
/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