LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Kylo Ginsberg <kylo.ginsberg@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Memtest-SDRAM
Date: Sun, 20 Nov 2005 21:30:56 +0100	[thread overview]
Message-ID: <20051120203056.11EAB353F54@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 20 Nov 2005 10:58:26 PST." <61cc712d0511201058p367df361i7e46591336918712@mail.gmail.com>

In message <61cc712d0511201058p367df361i7e46591336918712@mail.gmail.com> you wrote:
>
> > A simple test is: if Linux is running  without  problems  under  load
> > than there are no problems with your SDRAM.
> 
> Yes, but determining the proper load to test with can be tricky. 

Ummm.. I disagree. Avtually it's pretty simple. Boot the system  with
root  file  system  mounted  over  NFS.  The  compile  a Linux kernel
natively on the board. This is doing all you want: stressing  network
(lots  of  DMA),  stressing  the memory (lots of context switches and
heavy RAM use), etc. If your system survives this,  you  can  be  98%
sure that it will pass any other test as well.

> E.g., I had a subtle memory timing issue that only turned up under
> very peculiar circumstances under linux; this was very difficult to

Of course there are really weird cases,  but  fortunaltey  these  are
rare exceptions.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Committee, n.:  A group of men who individually can do nothing but as
a group decide that nothing can be done.                 - Fred Allen

      reply	other threads:[~2005-11-20 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  4:33 Memtest-SDRAM srideep.devireddy
2005-11-19 15:24 ` Memtest-SDRAM Wolfgang Denk
2005-11-20 18:58   ` Memtest-SDRAM Kylo Ginsberg
2005-11-20 20:30     ` Wolfgang Denk [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=20051120203056.11EAB353F54@atlas.denx.de \
    --to=wd@denx.de \
    --cc=kylo.ginsberg@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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