On Fri, Aug 7, 2015 at 9:40 AM, Sasha Levin <sasha.levin@xxxxxxxxxx> wrote: > On 08/07/2015 12:39 PM, Kevin Hilman wrote: >> On Fri, Aug 7, 2015 at 9:34 AM, kernelci.org bot <bot@xxxxxxxxxxxx> wrote: >>> > stable-sasha boot: 342 boots: 6 failed, 336 passed (v3.18.19-51-gdf0e5109cfea) >>> > >>> > Full Boot Summary: http://kernelci.org/boot/all/job/stable-sasha/kernel/v3.18.19-51-gdf0e5109cfea/ >>> > Full Build Summary: http://kernelci.org/build/stable-sasha/kernel/v3.18.19-51-gdf0e5109cfea/ >>> > >>> > Tree: stable-sasha >>> > Branch: local/linux-3.18.y-queue >>> > Git Describe: v3.18.19-51-gdf0e5109cfea >>> > Git Commit: df0e5109cfea25f842bf99f567aac20ac9ef78fe >>> > Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git >>> > Tested: 77 unique boards, 18 SoC families, 27 builds out of 143 >>> > >>> > Boot Failures Detected: http://kernelci.org/boot/?v3.18.19-51-gdf0e5109cfea&fail >>> > >>> > arm: >>> > >>> > exynos_defconfig: >>> > exynos5420-arndale-octa_rootfs:nfs: 1 failed lab >>> > exynos5800-peach-pi_rootfs:nfs: 1 failed lab >>> > >>> > multi_v7_defconfig: >>> > hisi-x5hd2-dkb_rootfs:nfs: 1 failed lab >>> > >>> > multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y: >>> > qcom-apq8074-dragonboard: 1 failed lab >>> > qcom-msm8974-sony-xperia-honami: 1 failed lab >>> > >>> > hisi_defconfig: >>> > hisi-x5hd2-dkb_rootfs:nfs: 1 failed lab >> These NFS boot failures are expected fails because NFS isn't enabled >> by default in v3.14, we need to blacklist these. >> >> The qcom Thumb2 errors are new and rather peculiar and seem to be >> alignment related as they can be made to boot by simply adding a >> 4-char localversion string! I'm still looking into that, but it's not >> directly related to the stable queue. > > Interesting! Do you actually boot in on metal, or is it qemu? This is on metal. We only have a couple qemu targets in kernelci.org currently, most of our boards are metal. 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