+Sjoerd
On 05/01/18 00:12, Kevin Hilman wrote:
kernelci.org bot bot@kernelci.org writes:
stable-rc/linux-4.14.y boot: 118 boots: 4 failed, 113 passed with 1 offline (v4.14.11-15-g732141e47ee6)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14... Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.11-15-...
Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.11-15-g732141e47ee6 Git Commit: 732141e47ee614d70aeb8ad828a977ad19447e87 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 68 unique boards, 23 SoC families, 16 builds out of 185
Boot Regressions Detected:
TL;DR; All is well.
Same issues as reported for stable-rc/linux-4.4.y, but...
arm:
multi_v7_defconfig: armada-xp-linksys-mamba: lab-free-electrons: new failure (last pass: v4.14.11) tegra124-nyan-big: lab-collabora: failing since 1 day (last pass: v4.14.10-147-g61f3176f64e3 - first fail: v4.14.11) omap2plus_defconfig: am335x-boneblack: lab-collabora: new failure (last pass: v4.14.11)... this one is unique to 4.14, but is still a lab issue: bootloader fails to DHCP.
Turns out this is a known hardware issue with the ethernet phy on this type of board. It's possible to work around it (retry...), we'll take a look.
Guillaume