On Tue, Feb 06, 2018 at 08:32:27AM +0000, Guillaume Tucker wrote:
On 05/02/18 22:52, kernelci.org bot wrote:
stable-rc/linux-3.18.y boot: 55 boots: 3 failed, 49 passed with 3 offline (v3.18.93-37-g384173e07d16)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18... Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.93-37-...
Tree: stable-rc Branch: linux-3.18.y Git Describe: v3.18.93-37-g384173e07d16 Git Commit: 384173e07d16663b09a8e4eae0d038e4d625e5fe Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 26 unique boards, 12 SoC families, 13 builds out of 167
Boot Regressions Detected:
arm:
exynos_defconfig: exynos4412-odroidx2: lab-collabora: new failure (last pass: v3.18.93-36-gfc50e0e1d16b)This was a temporary lab issue, resubmitted job boots fine:
https://lava.collabora.co.uk/scheduler/job/1064187
However the nfsroot fails and has always failed actually:
https://lava.collabora.co.uk/scheduler/job/1064188
This is simply due to the fact that the exynos_defconfig doesn't have CONFIG_ROOT_NFS enabled on 3.18.y even though it is in multi_v7_defconfig. So either we stop testing nfsroot on 3.18.y with exynos_defconfig, or we patch exynos_defconfig to make it work. I can submit the patch below if we want the latter.
I think the patch is a good idea.
thanks,
greg k-h