linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kunal Arya" <kunalarya@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel locked at "Now booting the kernel", Xilinx ML310 PPC405GP
Date: Fri, 9 Mar 2007 14:44:25 -0700	[thread overview]
Message-ID: <528646bc0703091344t28c57cc3yf60980dfe748cad1@mail.gmail.com> (raw)
In-Reply-To: <68ee5ad90703091309s64018616v3ba2b25033e84844@mail.gmail.com>

On 3/9/07, Kunal Arya <kunalarya@gmail.com> wrote:
> I'm currently working on getting Linux running on the Xilinx ML310.
> I've followed all of the directions so far, but have run into a boot
> problem.
>
> I used the kernel sources from Montavista's RSYNC servers, using this command:
> rsync -avz source.mvista.com::linuxppc-2.4 .
>
> This appears to be kernel version 2.4.30-pre1, according to version.h

Oh, ick.  you might want to try 2.6.  2.4 is so crusty (but I do have
2.4 working on my virtex boards, so it's not unusable).  :-)

What's probably happening, is some code is trying to access device
registers after the MMU is turned on, but before ioremap is called on
the registers.  I've had this situation before.  I usually just trace
through the boot path to find out how far it gets before the trap so I
know which device driver is at fault.

If you can access memory, it's also useful to look at the contents of
__log_buf after the crash.  That will tell you approximately how far
boot proceeded.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-03-09 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 21:09 Kernel locked at "Now booting the kernel", Xilinx ML310 PPC405GP Kunal Arya
2007-03-09 21:44 ` Grant Likely [this message]
2007-03-12 13:42 ` Mike Dyer
2007-03-20  3:31   ` Kunal Arya

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=528646bc0703091344t28c57cc3yf60980dfe748cad1@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=kunalarya@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).