From: Dave Liu <r63238@freescale.com>
To: Lei Sun <leisun124@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: memory corruption after MMU turned on
Date: Sun, 19 Nov 2006 14:01:42 +0800 [thread overview]
Message-ID: <1163916102.3655.20.camel@localhost.localdomain> (raw)
In-Reply-To: <f9a7e7a80611181353p21dce384m21f30bc9d8935a8d@mail.gmail.com>
On Sat, 2006-11-18 at 16:53 -0500, Lei Sun wrote:
> I tried enable i-cache, but it looks fine, however if i enable
Okay, That means the burst read memory is right. I think you should
check the code at the else, not only focus on RFI. Maybe the problem is
at the else position. When kernel boot stop, can not see any more
printed message, you can attach to the process with CW and USBTAP. see
where the current program pointer is.
> d-cache, u-boot corrupted right away, debugger showed some garbage
> memory instead of valid instruction.
<snip>
next prev parent reply other threads:[~2006-11-19 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 15:44 memory corruption after MMU turned on Lei Sun
[not found] ` <1628E43D99629C46988BE46087A3FBB97AFFDC@ep-01.EmbeddedPlanet.local>
2006-11-16 16:42 ` Lei Sun
2006-11-17 8:48 ` Dave Liu
2006-11-17 16:47 ` Lei Sun
2006-11-18 10:03 ` Dave Liu
2006-11-18 21:53 ` Lei Sun
2006-11-19 0:48 ` Wolfgang Denk
2006-11-19 6:01 ` Dave Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 16:11 Claus Gindhart
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=1163916102.3655.20.camel@localhost.localdomain \
--to=r63238@freescale.com \
--cc=leisun124@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;
as well as URLs for NNTP newsgroup(s).