From: Orion Poplawski <orion@cora.nwra.com>
To: scott@thomasons.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Reliable hardware
Date: Wed, 11 Dec 2002 09:08:34 -0700 [thread overview]
Message-ID: <3DF76302.7040503@cora.nwra.com> (raw)
In-Reply-To: 200212102000.54287.scott@thomasons.org
scott thomason wrote:
>On Tuesday 10 December 2002 03:00 pm, Alan Cox wrote:
>
>
>>Random lockups on dual athlons are a notorious problem under all
>>OS's. Start by checking it passes memtest86, that will verify the
>>RAM is ok - and the AMD is -very- picky about RAM.
>>
>>If thats ok then let me know which board you have, what is plugged
>>into it and what PSU you are using.
>>
>>
>
>I have two AMD MP 2000+ cpus in an ASUS A7M266-D. Even after returning
>my memory for new chips the store owner memtest86'd, my combo of cpus
>and mobo was finding the occasional error. I finally ended up
>resolving it by simply underclocking the bus about 6Mhz :(
>
>Next time, I'm buying ECC memory.
>---scott
>
>
Is there a good site for pointers towards assembling reliable Linux
machines? It seems to me the trickiest part of the whole operation is
choosing good hardware in the first place. I just started a new job and
inherited a buch of new but flakey machines, and I'd like to avoid doing
that in the future.
next prev parent reply other threads:[~2002-12-11 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 17:49 Oops on linux 2.4.20-ac1 Orion Poplawski
2002-12-10 21:00 ` Alan Cox
2002-12-11 2:00 ` scott thomason
2002-12-11 16:08 ` Orion Poplawski [this message]
2002-12-11 16:33 ` Reliable hardware John Bradford
2002-12-11 17:01 ` Alan Cox
2002-12-11 17:21 ` Jason L Tibbitts III
2002-12-11 23:35 ` Patrick Finnegan
2002-12-12 1:24 ` Alan Cox
2002-12-11 16:10 ` Oops on linux 2.4.20-ac1 Orion Poplawski
2002-12-11 23:00 ` Orion Poplawski
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=3DF76302.7040503@cora.nwra.com \
--to=orion@cora.nwra.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@thomasons.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