linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike Dyer <michaelidyer@gmail.com>
To: Kunal Arya <kunalarya@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel locked at "Now booting the kernel", Xilinx ML310 PPC405GP
Date: Mon, 12 Mar 2007 13:42:04 +0000	[thread overview]
Message-ID: <45F558AC.9060205@gmail.com> (raw)
In-Reply-To: <68ee5ad90703091309s64018616v3ba2b25033e84844@mail.gmail.com>

Hi Kunal,

Apologies if I post this twice - our mail server is unreliable atm...
> <snip>
> I used crosstool with gcc 4.1.1 w/glibc 2.3.6. My xparameters_ml300.h
> and .config files are pasted below.
>
> The problem:
> The kernel panics after printing out the message "Now booting the
> kernel" The exact output is this:
>
> loaded at:     00400000 0089C1E4
> board data at: 00000000 00000018
> relocated to:  00405238 00405250
> zimage at:     00405BD3 004AFDF5
> initrd at:     004B0000 00898382
> avail ram:     0089D000 55555555
>
> Linux/PPC load: root=/dev/ram
> Uncompressing Linux...done.
> Now booting the kernel
>
>
>   
I had the exact same problem for a different board, using the PPC in a 
Virtex 4 FX12, using the 2.6 kernel.  I fixed this by rolling the 
compiler back to version 4.0.2.  Didn't do a lot of thinking about why 
it worked, but I think it has something to do with the linker and your 
board data (it randomly changed location every time I tried to boot).  I 
believe it should be in the 0x00400000 range as well (not 0x00 as it is 
in your capture).

As a side note: Are there any known issues using GCC 4.1.1?

Cheers,
Mike

  parent reply	other threads:[~2007-03-12 13:42 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
2007-03-12 13:42 ` Mike Dyer [this message]
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=45F558AC.9060205@gmail.com \
    --to=michaelidyer@gmail.com \
    --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).