On 09/16/2013 07:55 PM, Jonathan Masters wrote:
If someone can capture a full backtrace then I will look. I will also
aim to reproduce myself a few more times. I am told there is a JTAG option but have not
looked further since the weekend yet.
I've tried, but I think what I've already posted is all the
backtrace I can get.
Here is the strange thing. It looks like this is happening
while still in u-boot, but it appears to be dependent on
the kernel being loaded.
I realize that that doesn't make much sense, but here are my
reasons for that conclusion.
1) One of the failure cases prints "Wrong Image Format for",
which comes from u-boot/common/cmd_bootm.c
2) If the boot sequence gets as far as printing:
Starting kernel ...
then it will always boot successfully (for me, anyway). That
message comes from u-boot/arch/arm/lib/bootm.c
3) Another failure case prints:
MAYBE you should read doc/README.arm-unaligned-accesses
That comes from u-boot/arch/arm/lib/interrupts.c
I cannot explain why the specific kernel matters, unless the
size of the kernel matters. The uImage from Tapani's tree is
around 2 MB, while the Fedora one is closer to 5 MB.
I don't know if this makes it any easier to track down, but it
is the best data I've got right now.