stable-rc/linux-4.4.y boot: 96 boots: 5 failed, 82 passed with 4 offline, 4 untried/unknown, 1 conflict (v4.4.216-38-gde8c7dfeb84e) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.216-38-gde8c7dfeb84e/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.216-38-gde8c7dfeb84e/ Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.216-38-gde8c7dfeb84e Git Commit: de8c7dfeb84e46ca3605e713bcb385f85b7070f3 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 49 unique boards, 17 SoC families, 17 builds out of 190 Boot Regressions Detected: arm: qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 37 days (last pass: v4.4.212-56-g758a39807529 - first fail: v4.4.213-28-ga3b43e6eae91) sunxi_defconfig: gcc-8: sun4i-a10-cubieboard: lab-baylibre-seattle: failing since 6 days (last pass: v4.4.215-62-g1ef447a18aac - first fail: v4.4.215-73-g836f82655232) vexpress_defconfig: gcc-8: vexpress-v2p-ca9: lab-baylibre: failing since 1 day (last pass: v4.4.216 - first fail: v4.4.216-22-g0acb20f67a41) i386: i386_defconfig: gcc-8: qemu_i386: lab-baylibre: new failure (last pass: v4.4.216-22-g0acb20f67a41) Boot Failures Detected: arm: multi_v7_defconfig: gcc-8: sun4i-a10-cubieboard: 1 failed lab sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab multi_v5_defconfig: gcc-8: imx27-phytec-phycard-s-rdk: 1 failed lab imx_v4_v5_defconfig: gcc-8: imx27-phytec-phycard-s-rdk: 1 failed lab sunxi_defconfig: gcc-8: sun4i-a10-cubieboard: 1 failed lab Offline Platforms: arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) i386: i386_defconfig: qemu_i386: lab-collabora: PASS (gcc-8) lab-baylibre: FAIL (gcc-8) --- For more info write to <info@xxxxxxxxxxxx>