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.

Guillaume

--- >8 ---

diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index e21ef830a483..999ea477be54 100644 --- a/arch/arm/configs/exynos_defconfig +++ b/arch/arm/configs/exynos_defconfig @@ -33,6 +33,10 @@ CONFIG_PACKET=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y +CONFIG_IP_PNP=y +CONFIG_IP_PNP_DHCP=y +CONFIG_IP_PNP_BOOTP=y +CONFIG_IP_PNP_RARP=y CONFIG_RFKILL_REGULATOR=y CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_DEVTMPFS=y @@ -170,6 +174,10 @@ CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_CRAMFS=y CONFIG_ROMFS_FS=y +CONFIG_NFS_FS=y +CONFIG_NFS_V3_ACL=y +CONFIG_NFS_V4=y +CONFIG_ROOT_NFS=y CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y