On Feb 10, 2015, at 12:19 AM, Kevin's boot bot khilman@kernel.org wrote:

Full Build report: http://kernelci.org/build/mainline/kernel/v3.19-463-g3e8c04eb1174/ Full Boot report: http://kernelci.org/boot/all/job/mainline/kernel/v3.19-463-g3e8c04eb1174/

Tree/Branch: mainline Git describe: v3.19-463-g3e8c04eb1174

Failed boot tests

   qcom-apq8074-dragonboard:     FAIL:    arm-multi_v7_defconfig+CONFIG_PROVE_LOCKING=y
                                 kernel: ERROR: did not start booting.
                                 http://storage.kernelci.org/kernel-ci/mainline/v3.19-463-g3e8c04eb1174/arm-multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/lab-khilman/boot-qcom-apq8074-dragonboard.html

Is this really a kernel fail? From the log wondering about ‘Command not recognised’ message.

# PYBOOT: fastboot: loading tmp/dragon-0CQtBi/zImage, tmp/dragon-0CQtBi/tmpiiwLCY.dtb, tmp/dragon-0CQtBi/rootfs.cpio.gz

~$fastboot -t 192.168.1.3 tmp/dragon-0CQtBi/zImage tmp/dragon-0CQtBi/tmpiiwLCY.dtb tmp/dragon-0CQtBi/rootfs.cpio.gz

Command(dragon console)> fastboot -t 192.168.1.3 tmp/dragon-0CQtBi/zImage tmp/dragon-0CQtBi/tmpiiwLCY.dtb tmp/dragon-0CQtBi/rootfs.cpio.gz Command not recognised ~$off

- k