Regression due to: arm: Add Prep subcommand support to bootm

U-Boot Stephen Warren 2 participants 3 messages Apr 12, 2012 – Apr 13, 2012

lore

Share & tools

lore

Stephen Warren

author

2012-04-12 16:52 UTC #0 lore raw

I just tried the latest u-boot/master, at commit:

3f0675d Merge branch 'marek.vasut at gmail.com' of
git://git.denx.de/u-boot-staging

This fails to boot a Linux kernel on my ARM Tegra board; the boot log is:

====================
## Booting kernel from Legacy Image at 00408000 ... Image Name: Linux-3.4.0-rc1-next-20120405-00
Image Type: ARM Linux Kernel Image (no loading done) (uncompressed) Data Size: 2756424 Bytes = 2.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x01000000
XIP Kernel Image (no loading done) ... OK
OK
Loading Device Tree to 010fa000, end 010ff726 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Warning: Neither atags nor dtb found
====================

If I revert commit 0a672d4 "arm: Add Prep subcommand support to bootm", then everything works fine again.

Tom Rini

2012-04-13 15:07 UTC #1 lore raw

Quoted 21 lines · Stephen Warren

I just tried the latest u-boot/master, at commit:
3f0675d Merge branch 'marek.vasut at gmail.com' of
git://git.denx.de/u-boot-staging
This fails to boot a Linux kernel on my ARM Tegra board; the boot log is:
====================
## Booting kernel from Legacy Image at 00408000 ... Image Name: Linux-3.4.0-rc1-next-20120405-00
Image Type: ARM Linux Kernel Image (no loading done) (uncompressed) Data Size: 2756424 Bytes = 2.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x01000000
XIP Kernel Image (no loading done) ... OK
OK
Loading Device Tree to 010fa000, end 010ff726 ... OK

Quoted 8 lines

Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Warning: Neither atags nor dtb found
====================
If I revert commit 0a672d4 "arm: Add Prep subcommand support to bootm", then everything works fine again.

I don't see this on beagleboard so we'll need some more tracking down of just how this broke tegra from you :( Thanks!

Signature · 8 lines

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120413/dc274747/attachment.pgp>

Stephen Warren

author

2012-04-13 20:19 UTC #2 lore raw

Quoted 29 lines · Tom Rini

Quoted 27 lines · Stephen Warren
I just tried the latest u-boot/master, at commit:
3f0675d Merge branch 'marek.vasut at gmail.com' of
git://git.denx.de/u-boot-staging
This fails to boot a Linux kernel on my ARM Tegra board; the boot log is:
====================
## Booting kernel from Legacy Image at 00408000 ... Image Name: Linux-3.4.0-rc1-next-20120405-00
Image Type: ARM Linux Kernel Image (no loading done) (uncompressed) Data Size: 2756424 Bytes = 2.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x01000000
XIP Kernel Image (no loading done) ... OK
OK
Loading Device Tree to 010fa000, end 010ff726 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Warning: Neither atags nor dtb found
====================

Quoted 5 lines

Quoted 2 lines
If I revert commit 0a672d4 "arm: Add Prep subcommand support to bootm", then everything works fine again.
I don't see this on beagleboard so we'll need some more tracking down of just how this broke tegra from you :( Thanks!

This only seems to affect booting with a device tree. Booting without passing a device tree works fine.

I also tested "mkimage -T kernel_noload" (which I typically use) vs. "mkimage -T kernel", and it makes no difference to either DT or non-DT boots, so that's one potentially unusual thing I do eliminated.