[U-Boot] image.h: Tighten up content using handy CONFIG_IS_ENABLED() macro: Causing Linux boot crash

[Tom Rini]

On Tue, May 31, 2016 at 02:32:06PM +0000, Prabhakar Kushwaha wrote:

> Hi Robert,
> 
> I was trying Linux boot on LS2080ARDB platform(ls2080ardb_defconfig) with top commit i.e. "e4a94ce4ac77396b181663c0493c50bc2d5b9143 ".
> 
> I am seeing below crash while trying to mount root file system. 
> 
> [    2.844331] NET: Registered protocol family 17
> [    2.848787] NET: Registered protocol family 15
> [    2.853251] 8021q: 802.1Q VLAN Support v1.8
> [    2.857455] 9pnet: Installing 9P2000 support
> [    2.861753] Key type dns_resolver registered
> [    2.866274] registered taskstats version 1
> [    2.870575] fsl_generic: FSL DPAA Generic Ethernet driver
> [    2.877144] rtc-ds3232 2-0068: setting system clock to 2016-02-08 05:34:04 UTC (1454909644)
> [    2.886344] List of all partitions:
> [    2.889831] 0100        33554432 ram0  (driver?)
> [    2.894450] 0101        33554432 ram1  (driver?)
> [    2.899077] 0102        33554432 ram2  (driver?)
> [    2.903695] 0103        33554432 ram3  (driver?)
> [    2.908318] 0104        33554432 ram4  (driver?)
> [    2.912935] 0105        33554432 ram5  (driver?)
> [    2.917557] 0106        33554432 ram6  (driver?)
> [    2.922175] 0107        33554432 ram7  (driver?)
> [    2.926800] 0108        33554432 ram8  (driver?)
> [    2.931417] 0109        33554432 ram9  (driver?)
> [    2.936035] 010a        33554432 ram10  (driver?)
> [    2.940743] 010b        33554432 ram11  (driver?)
> [    2.945447] 010c        33554432 ram12  (driver?)
> [    2.950153] 010d        33554432 ram13  (driver?)
> [    2.954857] 010e        33554432 ram14  (driver?)
> [    2.959565] 010f        33554432 ram15  (driver?)
> [    2.964272] 1f00          131072 mtdblock0  (driver?)
> [    2.969329] 1f01         2097152 mtdblock1  (driver?)
> [    2.974378] No filesystem could mount root, tried:  ext3 ext2 ext4 vfat fuseblk
> [    2.981713] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
> [    2.989979] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.8+ #1
> [    2.995896] Hardware name: Freescale Layerscape 2080a RDB Board (DT)
> [    3.002247] Call trace:
> [    3.004692] [<ffff800000089a44>] dump_backtrace+0x0/0x12c
> [    3.010089] [<ffff800000089b80>] show_stack+0x10/0x1c
> [    3.015139] [<ffff80000079ca3c>] dump_stack+0x8c/0xdc
> [    3.020189] [<ffff80000079a2d8>] panic+0xe4/0x220
> [    3.024890] [<ffff800000aa5f8c>] mount_block_root+0x248/0x270
> [    3.030635] [<ffff800000aa61fc>] mount_root+0x114/0x134
> [    3.035857] [<ffff800000aa6390>] prepare_namespace+0x174/0x1c0
> [    3.041688] [<ffff800000aa5b68>] kernel_init_freeable+0x1c0/0x1e8
> [    3.047779] [<ffff800000797e84>] kernel_init+0xc/0xdc
> [    3.052829] CPU7: stopping
> [    3.055534] CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.1.8+ #1
> [    3.061450] Hardware name: Freescale Layerscape 2080a RDB Board (DT)
> 
> 
> I did git bisect and figure out commit "56adbb38727320375b2f695bd04600d766d8a1b3" i.e.  "image.h: Tighten up content using handy CONFIG_IS_ENABLED() macro" causing this crash. 
> If I revert this patch, every things work perfectly. 
> 
> Any suggestion.. Am I missing something!!

No, just my fault here, sorry, pushing a fix shortly.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160531/42960dba/attachment.sig>