From: "john h" <johnh.nm@gmail.com>
To: linuxppc-embedded@ozlabs.org, u-boot@lists.denx.de
Subject: MV Linux uImage not working with u-boot, but zImage does
Date: Mon, 18 Aug 2008 16:25:00 -0600 [thread overview]
Message-ID: <a8299a810808181525h14a7bdcdt2f84fdb427ca4c24@mail.gmail.com> (raw)
I wasn't sure if this is a Linux issue or a u-boot issue.
We are using an older version of arch/ppc MontaVista Linux and having
a problem with u-boot. We can build a zImage and convert it to a
uImage and it runs from u-boot fine.
If we build a uImage from MV, the kernel crashes as shown below. We
are using u-boot version U-Boot 1.3.0-rc3.
Yet we can boot an arch/ppc Linux kernel (uImage) that's based on
2.6.26. Is there something we're not realizing that is different in
the u-boot interface?
Thanks,
John
version 2.6.10_mvl401-ml40x () (gcc version 3.4.3 (MontaVista 3.4.3
25.0.70.0501961
<4>mem_pieces_remove: [0,0) not in any region
<2>kernel BUG in free_bootmem_core at mm/bootmem.c:115!
<4>NIP: C02B4D04 LR: C02B2350 SP: C02A3F90 REGS: c02a3ee0 TRAP: 0700
Not tainted
<6>GPR00: 00000000 C02A3F90 C026C720 C02D6EAC 00000000 00000001
C0270000 C026DC48
<6>GPR08: C0270000 00000000 00000000 00000000 48002028 0000A5A5
10000C00 00000000
<6>GPR16: 007FFF00 00000000 007FFE80 00800000 00000000 00000000
0FFFA304 00000000
<6>GPR24: 00000000 0FEDA958 00000DC0 007FFF3A 007FFF00 C02D0000
00000001 C02CEC04
<4>NIP [c02b4d04] free_bootmem_core+0x1c/0xac
<4>LR [c02b2350] do_init_bootmem+0xfc/0x140<4> Call trace:
<4> [c02b1cec] setup_arch+0xd8/0x1dc
<4> [c02a44d8] start_kernel+0x28/0x1bc
<4> [c0000240] skpinv+0x1e8/0x224
<0>Kernel panic - not syncing: Attempted to kill the idle task!
<4> <0> Rebooting in 180 seconds..
reply other threads:[~2008-08-18 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a8299a810808181525h14a7bdcdt2f84fdb427ca4c24@mail.gmail.com \
--to=johnh.nm@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=u-boot@lists.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).