From: Adam Wozniak <adam.wozniak@comdev.cc>
To: Dan Malek <dan@mvista.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppcdev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: crash in fault.c
Date: Mon, 01 Oct 2001 15:36:55 -0700 [thread overview]
Message-ID: <3BB8F007.C68D53B6@comdev.cc> (raw)
In-Reply-To: 3BB8C658.38832E91@mvista.com
Dan Malek wrote:
>
> I suspect this is a hardware configuration problem in the
> memory controller or memory interface. As I have always said,
> random problems that occur when the network is used usually
> point to that. The reason is you can get back to back burst
> mode transfers to the memory, something you aren't likely
> to see with just normal CPU usage.
Ok. I'm a little new to this. How do I start troubleshooting
"a hardware configuration problem in the memory controller or
memory interface" ?
I'm using PPCBoot for a boot monitor, and VisionProbe for a JTAG
debugger. I've run a number of RAM tests, and don't seem to have
any problems reading/writing to RAM. What kind of thing am I
looking for?
--Adam
--
Adam Wozniak (KG6GZR) COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc 3450 Broad St. 107, San Luis Obispo, CA 93401
http://www.comdev.cc
Voice: (805) 544-1089 Fax: (805) 544-2055
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-01 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 18:19 crash in fault.c Adam Wozniak
2001-10-01 19:37 ` Benjamin Herrenschmidt
2001-10-01 19:39 ` Dan Malek
2001-10-01 22:36 ` Adam Wozniak [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 18:15 Adam Wozniak
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=3BB8F007.C68D53B6@comdev.cc \
--to=adam.wozniak@comdev.cc \
--cc=benh@kernel.crashing.org \
--cc=dan@mvista.com \
--cc=linuxppc-dev@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.