On 05/01/18 00:06, Kevin Hilman wrote:
kernelci.org bot bot@kernelci.org writes:
stable-rc/linux-4.4.y boot: 100 boots: 4 failed, 93 passed with 1 offline, 2 conflicts (v4.4.109-38-g99abd6cdd65e)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.1... Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.109-38-g...
Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.109-38-g99abd6cdd65e Git Commit: 99abd6cdd65e984d89c8565508a7a96ea0fce179 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 53 unique boards, 19 SoC families, 16 builds out of 178
TL;DR; All is well.
Boot Regressions Detected:
arm:
exynos_defconfig: exynos5422-odroidxu3: lab-collabora: failing since 58 days (last pass: v4.4.95-21-g32458fcb7bd6 - first fail: v4.4.96-41-g336421367b9c)Long standing issue in lab-collabora (passing in other labs) Guillaume?
This should be fixed now, with a tweak to the device config to enable relocating the ramdisk and dtb:
https://review.linaro.org/#/c/23238/
multi_v7_defconfig: armada-xp-linksys-mamba: lab-free-electrons: new failure (last pass: v4.4.109-36-g8b381424010c)Not a kerel issue, bootROM fails to start bootloader. I pinged lab owners (Free Electrons)
tegra124-nyan-big: lab-collabora: failing since 1 day (last pass: v4.4.109 - first fail: v4.4.109-36-g8b381424010c) tegra_defconfig: tegra124-nyan-big: lab-collabora: failing since 1 day (last pass: v4.4.108-65-g57856049c0f8 - first fail: v4.4.109)This one is booting fine, but the command to power-off the board is timing out, resulting in a failure report.
Indeed, this was due to a crash of the lavapdu daemon - it's back on track now.
(On a side note, the tegra124-nyan-big is still failing to boot in mainline due to a genuine kernel driver issue.)
Guillaume