Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> writes: > On Fri, 23 Aug 2019 at 04:10, Kevin Hilman <khilman@xxxxxxxxxxxx> wrote: >> >> "kernelci.org bot" <bot@xxxxxxxxxxxx> writes: >> >> > stable-rc/linux-4.4.y boot: 101 boots: 2 failed, 84 passed with 12 offline, 2 untried/unknown, 1 conflict (v4.4.189-79-gf18b2d12bf91) >> >> TL;DR; All is well. >> >> > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.189-79-gf18b2d12bf91/ >> > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.189-79-gf18b2d12bf91/ >> > >> > Tree: stable-rc >> > Branch: linux-4.4.y >> > Git Describe: v4.4.189-79-gf18b2d12bf91 >> > Git Commit: f18b2d12bf9162bef0b051e6300b389a674f68e1 >> > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> > Tested: 47 unique boards, 19 SoC families, 14 builds out of 190 > ... >> > Boot Failures Detected: >> > >> > arm64: >> > defconfig: >> > gcc-8: >> > qcom-qdf2400: 1 failed lab >> >> This one looks like the boot firmware is not even starting the kernel. >> The Linaro/LKFT lab folks will need to have a look. > > At LKFT lab arm64 juno-r2 is only the device for 4.4 upstream kernel testing. That might be your goal, but that's not what is happening. This boards is clearly being tested with v4.4 in kernelCI: https://kernelci.org/boot/qcom-qdf2400/ Looks like you may want to blacklist v4.4 for this board in kernelCI. Kevin
