Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > On Tue, Mar 08, 2016 at 02:11:08AM -0800, kernelci.org bot wrote: >> stable-queue boot: 205 boots: 14 failed, 190 passed with 1 offline (v4.4.4-74-gcc3ba9c14b31) >> >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-queue/kernel/v4.4.4-74-gcc3ba9c14b31/ >> Full Build Summary: https://kernelci.org/build/stable-queue/kernel/v4.4.4-74-gcc3ba9c14b31/ >> >> Tree: stable-queue >> Branch: local/linux-4.4.y.queue >> Git Describe: v4.4.4-74-gcc3ba9c14b31 >> Git Commit: cc3ba9c14b31161587ce85e9b5d642e730a2d0e8 >> Git URL: git://server.roeck-us.net/git/linux-stable.git >> Tested: 47 unique boards, 13 SoC families, 18 builds out of 132 >> >> Boot Failures Detected: https://kernelci.org/boot/?v4.4.4-74-gcc3ba9c14b31&fail >> >> arm: >> >> mxs_defconfig: >> imx23-olinuxino: 1 failed lab >> >> omap2plus_defconfig: >> omap4-panda: 1 failed lab >> >> multi_v7_defconfig+CONFIG_LKDTM=y: >> imx53-qsrb: 1 failed lab >> imx6dl-riotboard: 1 failed lab >> socfpga_cyclone5_socrates: 1 failed lab >> >> multi_v7_defconfig+CONFIG_SMP=n: >> imx53-qsrb: 1 failed lab >> imx6dl-riotboard: 1 failed lab >> socfpga_cyclone5_socrates: 1 failed lab >> >> multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y: >> socfpga_cyclone5_socrates: 1 failed lab >> >> imx_v6_v7_defconfig: >> imx53-qsrb: 1 failed lab >> imx6dl-riotboard: 1 failed lab >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: >> imx53-qsrb: 1 failed lab >> imx6dl-riotboard: 1 failed lab >> socfpga_cyclone5_socrates: 1 failed lab >> >> Offline Platforms: >> >> arm: >> >> mxs_defconfig: >> imx28-duckbill: 1 offline lab > > I really don't know what these mean, any chance you can distill these > down to "all is fine", or "there is a problem with this arch" type > emails? All is fine. These failures are are on newly added boards coming from a new lab and they're failing in other trees also, so we'll ignore them for now and check with the specific lab owner. Kevin -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html