On 04/16/2017 06:57 AM, kernelci.org bot wrote: > stable-rc/linux-4.4.y boot: 87 boots: 2 failed, 82 passed with 3 offline (v4.4.61-19-ge153e9e2397b) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.61-19-ge153e9e2397b/ > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.61-19-ge153e9e2397b/ > > Tree: stable-rc > Branch: linux-4.4.y > Git Describe: v4.4.61-19-ge153e9e2397b > Git Commit: e153e9e2397bd8b93af00fdf9a417568b342e271 > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 12 unique boards, 6 SoC families, 22 builds out of 201 > > Boot Regressions Detected: > > arm: > > multi_v7_defconfig+CONFIG_SMP=n: > exynos5250-snow: > lab-collabora: failing since 92 days (last pass: v4.4.40-59-g1d41ca34dce6 - first fail: v4.4.42-28-g707ffd8554f6) My understanding is that CONFIG_SMP=n is blacklisted for exynos. Are you testing this config now? I will follow up to see if !SMP use-case is important one to fix it. That said, I am not sure if this is a regression in the sense that, if !SMP ever worked on exynos. thanks, -- Shuah