On Fri, Jul 14, 2017 at 12:17:03PM +0100, Mark Brown wrote: > On Thu, Jul 13, 2017 at 03:07:46PM -0700, kernelci.org bot wrote: > > > > > multi_v7_defconfig > > imx6ul-pico-hobbit_rootfs:nfs: 1 failed lab > > > > mvebu_v5_defconfig > > kirkwood-openblocks_a7_rootfs:nfs: 1 failed lab > > > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > > omap4-panda: 1 failed lab > > These look at first glance labs were having a bad day. > > > sun5i-r8-chip: 1 failed lab > > This one isn't immediately obvious to me, the kernel got to the end of > boot then nothing from userspace: > > > https://storage.kernelci.org/stable-rc/linux-4.12.y/v4.12.1-11-g28917cd49df9/arm/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/lab-free-electrons/boot-sun5i-r8-chip.html > > > multi_v7_defconfig+CONFIG_SMP=n > > sun5i-r8-chip: 1 failed lab > > Same board, same symptoms. It's not booting in -next either in a > similar way so I'd not worry about it for now.
Ok, thanks for looking into these. greg k-h
