On 07/21/2014 11:23 PM, Kevin's boot bot wrote:
Full logs here: http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436
Tree/Branch: arm-soc Git describe: v3.16-rc5-772-gdf8c436 Failed boot tests ================= legacy,dm365evm: FAIL: arm-davinci_all_defconfig http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436/arm-davinci_all_... da850-evm: FAIL: arm-davinci_all_defconfig http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436/arm-davinci_all_... tegra124-jetson-tk1: FAIL: arm-tegra_defconfig http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436/arm-tegra_defcon... tegra30-beaver: FAIL: arm-tegra_defconfig http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436/arm-tegra_defcon... tegra124-jetson-tk1: FAIL: arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-772-gdf8c436/arm-multi_v7_def...
...
I assume these mass failures are some kind of initrd generation issue in your test scripts? The logs I looked at all failed with roughly:
Freeing unused kernel memory: 160K (c03f7000 - c041f000) request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c Failed to execute /init (error -8) Starting init: /sbin/init exists but couldn't execute it (error -8) Starting init: /bin/sh exists but couldn't execute it (error -8) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
Or did something go wrong with binfmts or binfmt module loading?