On Fri, Dec 22, 2017 at 04:11:16PM +0100, Greg Kroah-Hartman wrote: > On Fri, Dec 22, 2017 at 04:46:28AM -0800, kernelci.org bot wrote: > > stable-rc/linux-4.14.y boot: 136 boots: 12 failed, 111 passed with 12 offline, 1 untried/unknown (v4.14.8-159-gc2a94d1a6095) > > > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.8-159-gc2a94d1a6095/ > > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.8-159-gc2a94d1a6095/ > > > > Tree: stable-rc > > Branch: linux-4.14.y > > Git Describe: v4.14.8-159-gc2a94d1a6095 > > Git Commit: c2a94d1a60958294af33649f908960c536a206d5 > > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Tested: 76 unique boards, 23 SoC families, 17 builds out of 185 > > > > Boot Regressions Detected: > > > > arm: > > > > exynos_defconfig: > > exynos5250-arndale: > > lab-baylibre-seattle: failing since 6 days (last pass: v4.14.5-97-gcdda4aaafa84 - first fail: v4.14.6) > > > > arm64: > > > > defconfig: > > hip07-d05_rootfs:nfs: > > lab-collabora: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > meson-gxbb-p200: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > meson-gxl-s905d-p230: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > meson-gxl-s905x-khadas-vim: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > meson-gxl-s905x-nexbox-a95x: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > meson-gxl-s905x-p212: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > qemu: > > lab-mhart: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > lab-collabora: new failure (last pass: v4.14.8-64-g6b2f7746b2ea) > > r8a7796-m3ulcb: > > lab-collabora: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > rk3399-firefly: > > lab-baylibre-seattle: new failure (last pass: v4.14.8-63-gbbedfb07d3bf) > > These should all now be fixed with the -rc2 release, sorry about that. > > My arm64 box here is dead, so I couldn't test it locally :( Ok, the box now works just fine, it was my fault. I'm updating it right now and will get it up and working as part of my test systems next week. thanks, greg "oh the silver thing is a power button?" k-h