On Mon, Jul 03, 2017 at 12:25:48PM -0700, kernelci.org bot wrote: > stable-rc/linux-4.9.y boot: 130 boots: 5 failed, 112 passed with 13 offline (v4.9.35-173-g45949a8fd1df) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.35-173-g45949a8fd1df/ > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.35-173-g45949a8fd1df/ > > Tree: stable-rc > Branch: linux-4.9.y > Git Describe: v4.9.35-173-g45949a8fd1df > Git Commit: 45949a8fd1dfe62289359ae6e71bbb3fc45afeeb > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 31 unique boards, 13 SoC families, 28 builds out of 203 > > Boot Regressions Detected: > > arm: > > exynos_defconfig: > exynos5800-peach-pi_rootfs:nfs: > lab-collabora: new failure (last pass: v4.9.34-45-g92905e331aea) > > multi_v7_defconfig: > imx6q-sabrelite_rootfs:nfs: > lab-collabora: new failure (last pass: v4.9.34-44-g8041763f609c) > rk3288-rock2-square_rootfs:nfs: > lab-collabora: new failure (last pass: v4.9.34) > > mvebu_v5_defconfig: > kirkwood-openblocks_a7_rootfs:nfs: > lab-free-electrons: new failure (last pass: v4.9.34) Any hint as to why these new failures are happening? thanks, greg k-h