Re: am335x boot failure with CONFIG_DEBUG_RODATA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 14, 2016 at 05:43:30PM +0200, Alexander Aring wrote:
> Hi,
> 
> since commit 25362dc ("ARM: 8501/1: mm: flip priority of CONFIG_DEBUG_RODATA")
> which enables for (in my case) am335x CONFIG_DEBUG_RODATA by default, I notice
> that my beaglebone white doesn't boot anymore when this config is enabled.
> 
> I boot current linus/master via barebox v2016.04.0 with zImage format.
> The following message will be printed:
> 
> Error: unrecognized/unsupported machine ID (r1 = 0x00000ee0).
> 
> When I turn off CONFIG_DEBUG_RODATA it boots fine again.

Could you try booting with -v to print the addresses where the dtb gets
located?
If Russell is right then increasing image_decomp_size in
arch/arm/lib/bootm.c should help.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux