Re: [PATCH 3.18 00/21] 3.18.113-stable review

From: Greg Kroah-Hartman
Date: Wed Jun 13 2018 - 00:41:21 EST


On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote:
> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5 conflicts (v3.18.112-22-gb0582263e3c9)
>
> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/
> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/
>
> Tree: stable-rc
> Branch: linux-3.18.y
> Git Describe: v3.18.112-22-gb0582263e3c9
> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6
> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183
>
> Boot Regressions Detected:
>
> arm:
>
> bcm2835_defconfig:
> bcm2835-rpi-b:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> davinci_all_defconfig:
> dm365evm,legacy:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> exynos_defconfig:
> exynos5800-peach-pi:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> imx_v6_v7_defconfig:
> imx6dl-wandboard_dual:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> imx6dl-wandboard_solo:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> imx6q-wandboard:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> multi_v7_defconfig:
> am335x-boneblack:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> armada-xp-openblocks-ax3-4:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> exynos5800-peach-pi:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> imx6dl-wandboard_dual:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> imx6dl-wandboard_solo:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> imx6q-wandboard:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap3-beagle:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap3-beagle-xm:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap4-panda:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> sun4i-a10-cubieboard:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> sun7i-a20-cubietruck:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> tegra124-jetson-tk1:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> tegra20-iris-512:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> tegra30-beaver:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> zynq-zc702:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> mvebu_v7_defconfig:
> armada-xp-openblocks-ax3-4:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> omap2plus_defconfig:
> am335x-boneblack:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap3-beagle:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap3-beagle-xm:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap3-beagle-xm,legacy:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> omap4-panda:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> sama5_defconfig:
> at91-sama5d4ek:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> sunxi_defconfig:
> sun4i-a10-cubieboard:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> sun7i-a20-cubietruck:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
>
> tegra_defconfig:
> tegra124-jetson-tk1:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> tegra20-iris-512:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)
> tegra30-beaver:
> lab-baylibre-seattle: new failure (last pass: v3.18.112)

That is a lot of new failures, did the whole lab fail, or is this really
a problem in v3.18.112 here?

thanks,

greg k-h