From: Chris Zimman <chris@wmpp.com>
To: "Cordes, Aaron M" <aaron.m.cordes@lmco.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux 2.4.27-pre6-bk hangs on MPC8540 board
Date: Sat, 14 Aug 2004 09:40:56 -0500 [thread overview]
Message-ID: <20040814144056.GA9300@dingdong.cryptoapps.com> (raw)
In-Reply-To: <EE7CAF713952AC4A970DD7CD8B4C12A042DCAD@emss09m06.us.lmco.com>
On Thu, Aug 12, 2004 at 05:07:30PM -0500, Cordes, Aaron M wrote:
> I completely disabled L1 and L2 cache in the processor and I am not
> seeing the memory corruption anymore. So, good news is board is now
> booting, bad news is it's dog slow and we have a memory design to debug.
> Thanks to everyone for your prompt and helpful advice.
Before you spend too much time debugging the memory design, did you follow
Wolfgang's advice and take another look at your memory controller setup?
If it's working with cache disabled, and then failing in burst mode, 9 out of
10 times, it's because the SDRAM controller setup is wrong. It only has to
be very subtly wrong to fail like this.
If you're using DIMMs versus having memory right on the board, are you
reading from the SPD for the config parameters?
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-14 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 22:07 Linux 2.4.27-pre6-bk hangs on MPC8540 board Cordes, Aaron M
2004-08-13 14:30 ` Kumar Gala
2004-08-14 14:40 ` Chris Zimman [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 22:14 Swarthout Edward L-SWARTHOU
2004-08-12 19:38 Cordes, Aaron M
2004-08-12 22:11 ` Kumar Gala
2004-08-12 22:18 ` Conor McLoughlin
2004-08-12 19:34 Cordes, Aaron M
2004-08-12 12:47 Cordes, Aaron M
2004-08-12 13:09 ` Marc Leeman
2004-08-12 14:07 ` Wolfgang Denk
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=20040814144056.GA9300@dingdong.cryptoapps.com \
--to=chris@wmpp.com \
--cc=aaron.m.cordes@lmco.com \
--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.