All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: help with next generation bkbits please
Date: Mon, 20 Sep 2004 18:22:08 -0700	[thread overview]
Message-ID: <20040921012208.GA16008@work.bitmover.com> (raw)

Hi,

we're trying to upgrade bkbits.net for your pushing&pulling pleasure
and we're having some problems.

We wanted to throw lots of memory at the problem so we went with an
ASUS SK8V motherboard, opteron 148, 4 x 1GB registered / ECC dimms.
We thought we would be careful so we bought dimms that ASUS claims works.

We can't get the system to stabilize and we're looking for either 
    a) information on how to do that or
    b) a suggestion for a machine which will support 4GB or more

What we are currently seeing looks like a cache writeback problem.
I have a simple memory scrubber, see below, which just cycles through a
series of patterns, verifying the previous one and writing a new one,
switch pattern, repeat until pattern list is exhausted, then loop.
We cycle through the offset into the array, 0xdeadbeef, 0x50505050,
0x0a0a0a0a, 0x55555555, 0xaaaaaaaa, 0, 0xffffffff.

What we see is that for 16x4 bytes in a row we will get errors where
what we get is the previous value.  In other words, we just went through
a loop that verified that all the data is 0xdeadbeef and then set it
to 0x50505050, and then in the next loop 16 values will be 0xdeadbeef.
In other words, it looks like the cache writeback didn't work, it's as
if the dirty bits were cleared for some reason.

Does anyone have any idea what might be causing this and what we need
to do to fix it?  We'd really like to get you guys a nicer machine.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

             reply	other threads:[~2004-09-21  1:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  1:22 Larry McVoy [this message]
2004-09-21  1:25 ` help with next generation bkbits please Larry McVoy
2004-09-21  8:13 ` Denis Vlasenko

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=20040921012208.GA16008@work.bitmover.com \
    --to=lm@bitmover.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.