From: Alex Shnitman <alexsh@hectic.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Sandpoint & random crashes?
Date: Tue, 12 Sep 2000 09:57:51 +0300 [thread overview]
Message-ID: <20000912095751.A20541@hectic.net> (raw)
In-Reply-To: <000301c01c4b$6a7ac6d0$4d012ac7@warp-speed>; from ronb@junction.net on Mon, Sep 11, 2000 at 04:53:00PM -0700
Hi, Ron!
On Mon, Sep 11, 2000 at 04:53:00PM -0700, you wrote the following:
> Another possible hardware related problem might be that the Dink
> monitor is not programming the SDRAM controller with the right
> parameters for that DIMM module ( I assume the sandpoint uses DIMMs
> ). I'm not sure if the monitor reads the param data from the
> module's eeprom or is manually configured and stored in CMOS ram.
It's a SIMM module. Does that make any difference?
(You can see it at:
http://www.mot.com/SPS/PowerPC/teksupport/refdesigns/sandpoint.html#7400 )
> Anyway, have you run any memory tests?
No, how do I do that? What memory test applications are there for this
platform?
--
Alex Shnitman | http://www.debian.org
alexsh@hectic.net, alexsh@linux.org.il +-----------------------
http://alexsh.hectic.net UIN 188956 PGP key on web page
E1 F2 7B 6C A0 31 80 28 63 B8 02 BA 65 C7 8B BA
/real/ kernel hackers
dd if=/dev/urandom of=/vmlinuz
and influence the Universal Randomosity Field.
-- Gaal Yahas
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-12 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 1:32 Sandpoint & random crashes? ZHANG,HAI-TAO (Non-A-China,ex1)
2000-09-11 20:35 ` Mark A. Greer
2000-09-11 21:12 ` Alex Shnitman
2000-09-11 23:11 ` Mark A. Greer
2000-09-11 23:53 ` Ron Bianco
2000-09-12 6:57 ` Alex Shnitman [this message]
2000-09-18 14:13 ` Alex Shnitman
2000-09-18 17:42 ` Mark A. Greer
-- strict thread matches above, loose matches on Subject: below --
2000-09-12 1:25 ZHANG,HAI-TAO (Non-A-China,ex1)
2000-09-12 17:44 ` Mark A. Greer
2000-09-10 19:49 Alex Shnitman
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=20000912095751.A20541@hectic.net \
--to=alexsh@hectic.net \
--cc=linuxppc-embedded@lists.linuxppc.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.