public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dale Harris <rodmur@maybe.org>
To: linux-kernel@vger.kernel.org
Subject: dual AMD MP 2000+ and ASUS A7M266-D problems
Date: Fri, 14 Mar 2003 15:12:27 -0800	[thread overview]
Message-ID: <20030314231227.GA19468@maybe.org> (raw)

Hi,

I have a small cluster of systems with:

dual AMD MP 2000+
ASUS A7M266-D motherboard
2GB RAM... DIMMs are Crucial 512MB, DDR, 266Mhz, CL2.5, ECC
I'm running 2.4.20 (Debian, or vanilla, didn't seem to matter)

The only stable configuration I can seem to get is 1 CPU and 1 DIMM.
Every other setup Cerberus just blows up in anywhere from 10 minutes to
a little over 2 hrs.  Sometimes I see an oops, other times it just stops
dead and no interrupts are handled (caps lock doesn't turn on the little
light on the keyboard).  I saw a similar conversations in the archive
about a setup similar to this and various solutions, one being to
underclock the CPUs, suggesting, I guess that CPU heat is a problem
(even though I never see an alarm out of lm_sensors).  I did update the
board to the latest BIOS (1009), that doesn't seem to have any effect.  

testing with Cerberus:

1 CPU/ 1 DIMM run all the time
2 CPU/ 1 DIMM might run for 3 hours
1 or 2 CPU with more than 1 DIMM, lucky to last 20 minutes, usually
less.

I have tried each of the four DIMMs individually, they all appear to be
fine.  

So I'm wondering if anyone has any insight into what the problem might
be.  Is underclocking the chips all I can do?


-- 
Dale Harris   
rodmur@maybe.org
/.-)

             reply	other threads:[~2003-03-14 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 23:12 Dale Harris [this message]
2003-03-15  2:34 ` dual AMD MP 2000+ and ASUS A7M266-D problems Bruce Harada
2003-03-15  2:59   ` Dale Harris
2003-03-15 21:31     ` Heinz Ulrich Stille
2003-03-16  1:12 ` Alan Cox

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=20030314231227.GA19468@maybe.org \
    --to=rodmur@maybe.org \
    --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