On Thu, Oct 03, 2019 at 04:51:34PM -0700, Kevin Hilman wrote: > "kernelci.org bot" <bot@xxxxxxxxxxxx> writes: > > > stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline (v5.2.18-314-g2c8369f13ff8) > > > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/ > > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/ > > > > Tree: stable-rc > > Branch: linux-5.2.y > > Git Describe: v5.2.18-314-g2c8369f13ff8 > > Git Commit: 2c8369f13ff8c1375690964c79ffdc0e41ab4f97 > > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Tested: 80 unique boards, 27 SoC families, 16 builds out of 209 > > TL;DR; all is well. > > > Boot Failure Detected: > > > > arm64: > > defconfig: > > gcc-8: > > rk3399-firefly: 1 failed lab > > There's a known issue on this board I've been trying to debug with the > mediatek maintainers, and we're not sure yet if it's a kernel issue or > a hardware issue on my board, but for now, nothing to worry about for > stable. Thanks for the explaination and summary! greg k-h
