sequoia: The final kernel image would overwrite the device tree
benh at kernel.crashing.org
Sat Aug 8 07:03:11 EST 2009
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
> But depending on CONFIG_PROVE_LOCKING, the test for
> ((unsigned long)_end < ei.memsize) gives different results, and the
> 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.
More information about the Linuxppc-dev