On Thu, Nov 24, 2016 at 09:20:40PM -0800, kernelci.org bot wrote: > stable-rc boot: 207 boots: 8 failed, 196 passed with 3 offline (v4.8.10-68-g5b1cb43a9ac7) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8.10-68-g5b1cb43a9ac7/ > Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.8.10-68-g5b1cb43a9ac7/ > > Tree: stable-rc > Branch: local/linux-4.8.y > Git Describe: v4.8.10-68-g5b1cb43a9ac7 > Git Commit: 5b1cb43a9ac7f608fdfc590c139aa66ead8d19ed > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 57 unique boards, 18 SoC families, 30 builds out of 207 > > Boot Failures Detected: https://kernelci.org/boot/?v4.8.10-68-g5b1cb43a9ac7&fail > > arm: > > multi_v7_defconfig+CONFIG_SMP=n: > exynos5250-snow: 1 failed lab > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > at91-sama5d4_xplained: 1 failed lab > > exynos_defconfig: > exynos5250-arndale: 1 failed lab > > x86: > > defconfig+CONFIG_OF_UNITTEST=y: > x86-kvm: 1 failed lab > > defconfig+CONFIG_KASAN=y: > x86-kvm: 1 failed lab > > defconfig+CONFIG_LKDTM=y: > x86-kvm: 1 failed lab > > defconfig+kvm_guest: > x86-kvm: 1 failed lab > > x86_64_defconfig: > x86-kvm: 1 failed lab That's not good, is this a code problem, or a "lab" problem? The logs look like nothing is working for these, so is this a -rc problem? thanks, greg k-h -- 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