Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.11.4-84-ga598a2b Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: multi_v7_defconfig armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig
Full Report ===========
omap2plus_defconfig ------------------- omap3-beagle-xm PASS: 0 min 51.3 sec am335x-bone PASS: 0 min 26.5 sec omap3-tobi,3530overo PASS: 0 min 21.5 sec omap4-panda PASS: 1 min 5.4 sec omap4-panda-es PASS: 1 min 15.3 sec omap3-tobi,3730storm PASS: 0 min 24.4 sec omap3-beagle PASS: 0 min 50.5 sec
tegra_defconfig --------------- tegra30-beaver PASS: 0 min 15.4 sec
imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 15.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 15.8 sec
mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.8 sec armada-370-mirabox PASS: 0 min 18.3 sec
exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.9 sec
multi_v7_defconfig ------------------ tegra30-beaver PASS: 0 min 14.3 sec omap3-beagle-xm PASS: 0 min 51.7 sec armada-370-mirabox FAIL: 0 min 17.9 sec omap4-panda PASS: 0 min 58.9 sec armada-xp-openblocks-ax3-4 FAIL: 0 min 21.9 sec sun4i-a10-cubieboard PASS: 0 min 13.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 20.0 sec am335x-bone PASS: 0 min 38.6 sec omap4-panda-es PASS: 1 min 7.0 sec omap3-tobi,3730storm PASS: 0 min 22.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.3 sec omap3-beagle PASS: 1 min 31.9 sec
sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec
Console logs for failures =========================
multi_v7_defconfig ------------------
armada-370-mirabox: FAIL: last 24 lines of boot log: ----------------------------------------------------
[ 130.128962] usbhid: USB HID core driver [ 130.132991] TCP: cubic registered [ 130.136683] NET: Registered protocol family 10 [ 130.141598] sit: IPv6 over IPv4 tunneling driver [ 130.146667] Key type dns_resolver registered [ 130.150999] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 130.158723] Registering SWP/SWPB emulation handler [ 130.164093] ../../drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 130.171450] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 130.178947] Please append a correct "root=" boot option; here are the available partitions: [ 130.187335] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 130.195617] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.4-00084-ga598a2b #1 [ 130.202882] [<c00157bc>] (unwind_backtrace+0x0/0xf4) from [<c001168c>] (show_stack+0x10/0x14) [ 130.211429] [<c001168c>] (show_stack+0x10/0x14) from [<c04b143c>] (dump_stack+0x84/0x94) [ 130.219546] [<c04b143c>] (dump_stack+0x84/0x94) from [<c04ae960>] (panic+0xa0/0x1f0) [ 130.227308] [<c04ae960>] (panic+0xa0/0x1f0) from [<c06470ec>] (mount_block_root+0x1a0/0x230) [ 130.235764] [<c06470ec>] (mount_block_root+0x1a0/0x230) from [<c0647284>] (mount_root+0x108/0x110) [ 130.244741] [<c0647284>] (mount_root+0x108/0x110) from [<c06473e4>] (prepare_namespace+0x158/0x1a0) [ 130.253815] [<c06473e4>] (prepare_namespace+0x158/0x1a0) from [<c0646da8>] (kernel_init_freeable+0x1c8/0x1d8) [ 130.263751] [<c0646da8>] (kernel_init_freeable+0x1c8/0x1d8) from [<c04ac4bc>] (kernel_init+0x8/0x158) [ 130.272991] [<c04ac4bc>] (kernel_init+0x8/0x158) from [<c000e2b8>] (ret_from_fork+0x14/0x3c) # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 17.85 seconds. # PYBOOT: Result: FAIL
armada-xp-openblocks-ax3-4: FAIL: last 24 lines of boot log: ------------------------------------------------------------
[ 159.646327] [<c001168c>] (show_stack+0x10/0x14) from [<c04b143c>] (dump_stack+0x84/0x94) [ 159.654446] [<c04b143c>] (dump_stack+0x84/0x94) from [<c04ae960>] (panic+0xa0/0x1f0) [ 159.662214] [<c04ae960>] (panic+0xa0/0x1f0) from [<c06470ec>] (mount_block_root+0x1a0/0x230) [ 159.670676] [<c06470ec>] (mount_block_root+0x1a0/0x230) from [<c0647284>] (mount_root+0x108/0x110) [ 159.679661] [<c0647284>] (mount_root+0x108/0x110) from [<c06473e4>] (prepare_namespace+0x158/0x1a0) [ 159.688737] [<c06473e4>] (prepare_namespace+0x158/0x1a0) from [<c0646da8>] (kernel_init_freeable+0x1c8/0x1d8) [ 159.698680] [<c0646da8>] (kernel_init_freeable+0x1c8/0x1d8) from [<c04ac4bc>] (kernel_init+0x8/0x158) [ 159.707926] [<c04ac4bc>] (kernel_init+0x8/0x158) from [<c000e2b8>] (ret_from_fork+0x14/0x3c) [ 159.716387] CPU1: stopping [ 159.719102] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.11.4-00084-ga598a2b #1 [ 159.726353] [<c00157bc>] (unwind_backtrace+0x0/0xf4) from [<c001168c>] (show_stack+0x10/0x14) [ 159.734903] [<c001168c>] (show_stack+0x10/0x14) from [<c04b143c>] (dump_stack+0x84/0x94) [ 159.743017] [<c04b143c>] (dump_stack+0x84/0x94) from [<c0013b74>] (handle_IPI+0x10c/0x134) [ 159.751306] [<c0013b74>] (handle_IPI+0x10c/0x134) from [<c00086a4>] (armada_370_xp_handle_irq+0x90/0xa8) [ 159.760814] [<c00086a4>] (armada_370_xp_handle_irq+0x90/0xa8) from [<c0012180>] (__irq_svc+0x40/0x50) [ 159.770055] Exception stack(0xee873fa0 to 0xee873fe8) [ 159.775121] 3fa0: c22dc920 00000000 000009ee 000009ee c074e175 c06c44c0 c04bb204 ee872000 [ 159.783322] 3fc0: c074e175 ee872000 ee872000 c06c4448 00000000 ee873fe8 c000f430 c00797d0 [ 159.791518] 3fe0: 60000113 ffffffff [ 159.795023] [<c0012180>] (__irq_svc+0x40/0x50) from [<c00797d0>] (cpu_startup_entry+0x100/0x144) [ 159.803834] [<c00797d0>] (cpu_startup_entry+0x100/0x144) from [<000088a4>] (0x88a4) # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 21.90 seconds. # PYBOOT: Result: FAIL
On Wed, Oct 9, 2013 at 8:22 AM, Kevin Hilman build bot khilman@linaro.org wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.11.4-84-ga598a2b Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: multi_v7_defconfig armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig
For those keeping track, these mvebu failures are because multi_v7_defconfig does not currently enable CONFIG_ARM_ATAG_DTB_COMPAT, which is needed for u-boot to be able to pass an initramfs.
There is a patch submitted to stable to address this: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/202759.ht...
Kevin
On Wed, Oct 09, 2013 at 08:29:17AM -0700, Kevin Hilman wrote:
On Wed, Oct 9, 2013 at 8:22 AM, Kevin Hilman build bot khilman@linaro.org wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.11.4-84-ga598a2b Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: multi_v7_defconfig armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig
For those keeping track, these mvebu failures are because multi_v7_defconfig does not currently enable CONFIG_ARM_ATAG_DTB_COMPAT, which is needed for u-boot to be able to pass an initramfs.
There is a patch submitted to stable to address this: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/202759.ht...
Hang on a moment. If your test setup requires certain kernel options, you really should force those kernel options to appropriate values rather than relying on the defconfigs to conform to your own test infrastructure.
On Wed, Oct 9, 2013 at 8:33 AM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Wed, Oct 09, 2013 at 08:29:17AM -0700, Kevin Hilman wrote:
On Wed, Oct 9, 2013 at 8:22 AM, Kevin Hilman build bot khilman@linaro.org wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.11.4-84-ga598a2b Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: multi_v7_defconfig armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig
For those keeping track, these mvebu failures are because multi_v7_defconfig does not currently enable CONFIG_ARM_ATAG_DTB_COMPAT, which is needed for u-boot to be able to pass an initramfs.
There is a patch submitted to stable to address this: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-October/202759.ht...
Hang on a moment. If your test setup requires certain kernel options, you really should force those kernel options to appropriate values rather than relying on the defconfigs to conform to your own test infrastructure.
I agree in general.
In this particular case though, the patch submitted is to ensuring an existing fix that is already in mainline is also in stable.
Kevin
kernel-build-reports@lists.linaro.org