From: Chris Zimman <chris@cryptoapps.com>
To: Shenrong <rshen@udtech.com.cn>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC755 L2 Cache data parity error
Date: Mon, 16 Jun 2003 10:03:31 -0500 [thread overview]
Message-ID: <20030616150331.GB397@dingdong.cryptoapps.com> (raw)
In-Reply-To: <001401c3334f$c2e079f0$ca8d100a@justin>
On Sun, Jun 15, 2003 at 11:06:38PM +0800, Shenrong wrote:
> size to 512k or 256k, but don't know why. We use both the PBGA and
> CBGA packages, seems CBGA version are some more stable(still has problem),
> don't know why too.
The first thing I thought of when I read this is heat issues -- especially because
of the mention of PBGA vs. CBGA. Is your heat sinking/cooling adequate?
I had a problem once with a custom 405GP board that was not entirely dissimilar.
Running the OpenSSL 'speed' benchmark, the system would lock up doing the MD2 tests.
I couldn't fathom how a userland program could lockup the entire system. One day,
just by chance, I happened to stand the board on end -- no more crashes. The
difference had been the airflow underneath the device because it didn't have a
heatsink on it. Consequently, I put a heatsink on the 405 and that fixed the
problem altogether.
> It's more strange that I can simply let the error occur under Linux with
> continuous file copying in ram disk. But I can't let it occur under PPCBoot
> with whatever memory operations for even one time, whether use the L2 Cache
> memory as L2 Cache or as private memory. The L2 Cache has the same setting
> in the above two circumstances.
The only difference I could think of right away here is that under
Linux, you're doing burst reads and writes.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-16 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 15:06 MPC755 L2 Cache data parity error Shenrong
2003-06-16 15:03 ` Chris Zimman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 13:07 Chuck Brown
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=20030616150331.GB397@dingdong.cryptoapps.com \
--to=chris@cryptoapps.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rshen@udtech.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).