linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Deepak Gaur" <dgaur@cdotd.ernet.in>
To: "David Baird" <dhbaird@gmail.com>, linuxppc-embedded@ozlabs.org
Subject: Re: MVL Linux on MPC8560 Booting goes into infinite loop inearly_init memset_io ( )
Date: Tue, 8 Apr 2008 17:45:52 +0630	[thread overview]
Message-ID: <20080408110411.M21892@cdotd.ernet.in> (raw)
In-Reply-To: <440abda90804071250v60bd970fh938e9690836ab61@mail.gmail.com>

Hi,

Thanks for valuable inputs.. memset_io() issue got resolved after I invalidated the L1
data and Instruction cache before calling early_init(was mentioned in some mailing list
). The code execution resumed and somewhere during MMU_init it again got struck.This
time its due to a DataTLBError. I am now trying to trace the function causing TLB miss
using ICE Trace32. Any pointers for reason behind generation of DataTLBError during MMU_init

Thanks  

Deepak Gaur
On Mon, 7 Apr 2008 13:50:04 -0600, David Baird wrote
> On Mon, Apr 7, 2008 at 10:04 AM, Scott Wood <scottwood@freescale.com> wrote:
> >  BTW, it's generally bad form to post the same question repeatedly.  If you
> > have new information regarding your problem, just post a followup in the
> > same thread containing the new information.
> 
> Agreed!  I was about to respond to your new post, and then I
> discovered this nearly identical slightly older post.
> 
> On Mon, Apr 7, 2008 at 12:37 AM, Deepak Gaur <gaur.deepak@gmail.com> wrote:
> > While booting MVL linux on MPC8560 based board the kernel goes into a
> > infinite loop in setup.c
> 
> Someone please correct me if I am wrong, but those symbols inside the
> BSS should only be variables (not functions....) which are initialized
> to zero.  The whole reason for BSS is to initialize variables to a
> 0/null value.
> 
> Now, about the infinite loop.  Can you check to see if perhaps you are
> getting an exception?
> 
> I have no experience with the MPC8560, but I've seen a couple problems
> that occur involving memset_io.  What happens is that a TLB miss
> exception occurs when the CPU gets inside of memset_io.  Do you have
> the ability to check that with a debugger (by setting breakpoints at
> exceptions, such as the data and instruction TLB miss exceptions) to
> see if you are getting exceptions?
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Deepak Gaur

      parent reply	other threads:[~2008-04-08 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  6:49 MVL Linux on MPC8560 Booting goes into infinite loop in early_init memset_io ( ) Deepak Gaur
2008-04-07 16:04 ` Scott Wood
2008-04-07 19:50   ` David Baird
2008-04-07 19:56     ` David Baird
2008-04-08 11:15     ` Deepak Gaur [this message]

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=20080408110411.M21892@cdotd.ernet.in \
    --to=dgaur@cdotd.ernet.in \
    --cc=dhbaird@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).