From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Stefan Roese <sr@denx.de>
Subject: Re: sequoia: The final kernel image would overwrite the device tree
Date: Sat, 08 Aug 2009 07:03:11 +1000 [thread overview]
Message-ID: <1249678991.10143.1.camel@pasglop> (raw)
In-Reply-To: <alpine.LRH.2.00.0908071740410.22357@vixen.sonytel.be>
On Fri, 2009-08-07 at 17:48 +0200, Geert Uytterhoeven wrote:
> | Allocating 0x85e784 bytes for kernel ...
> | platform_ops.vmlinux_alloc = 0x00000000
> | _end = 0x792000
> | The final kernel image would overwrite the device tree?
>
> and it reboots.
>
> However, nm says _end = c085f000.
>
> So in both cases _end is not correct in
> arch/powerpc/boot/main.c:prep_kernel()?
> But depending on CONFIG_PROVE_LOCKING, the test for
> ((unsigned long)_end < ei.memsize) gives different results, and the
> kernel
> boots or doesn't boot?
>
Well, "Allocating 0x85e784" looks right...
My experience, however, with a Canyonlands board, is that uBoot has
a bug that makes it always allocate the device-tree below 8M and clash
with the kernel when it gets too big.
I think Stefan fixed that recently, you may need to rebuild your uboot,
I'll let him tell you the details about the fix.
Cheers,
Ben.
next prev parent reply other threads:[~2009-08-07 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 13:33 sequoia: The final kernel image would overwrite the device tree Geert Uytterhoeven
2009-08-07 15:48 ` Geert Uytterhoeven
2009-08-07 21:03 ` Benjamin Herrenschmidt [this message]
2009-08-08 7:38 ` Wolfgang Denk
2009-08-10 7:49 ` Geert Uytterhoeven
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=1249678991.10143.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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).