On 01/08/18 16:44, Guillaume Tucker wrote:
On 31/07/18 16:14, kernelci.org bot wrote:
next/master boot: 179 boots: 11 failed, 167 passed with 1 offline (next-20180731)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20180731/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20180731/
Tree: next Branch: master Git Describe: next-20180731 Git Commit: 85eac382fa06ac72adf891d04bf4d08fb09d80fa Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 66 unique boards, 26 SoC families, 21 builds out of 200
Boot Regressions Detected:
arm:
[...]> bcm2837-rpi-3-b:
lab-baylibre: failing since 1 day (last pass: next-20180727 - first fail: next-20180730)
I've run an automated bisection on kernelci.org which found this "bad" commit:
bb4b894addb09a069c072a0a032f644cc470d17f is the first bad commit commit bb4b894addb09a069c072a0a032f644cc470d17f Author: Srinivas Kandagatla srinivas.kandagatla@linaro.org Date: Fri Jul 13 16:36:28 2018 +0100
ASoC: core: add support to card re-bind using component framework This patch aims at achieving dynamic behaviour of audio card when the dependent components disappear and reappear. With this patch the card is removed if any of the dependent component is removed and card is added back if the dependent component comes back. All this is done using component framework and matching based on component name. Signed-off-by: Srinivas Kandagatla srinivas.kandagatla@linaro.org Reviewed-by: Vinod Koul vkoul@kernel.org Signed-off-by: Mark Brown broonie@kernel.org
The boot tests can all be found here for each step of the bisection with extra checks at the end:
http://lava.baylibre.com:10080/scheduler/alljobs?length=25&search=bisect...
Sorry, this is the correct link for this bisection:
http://lava.baylibre.com:10080/scheduler/alljobs?length=25&search=bisect...
I haven't investigated any further, just ran this boot bisection between next-20180731 and its common base with mainline/master. I'm not sure if this is at all related to the issue hit in next-20180724, probably not.
Hope this helps!
Best wishes, Guillaume
[...]
For more info write to info@kernelci.org
Kernel-build-reports mailing list Kernel-build-reports@lists.linaro.org https://lists.linaro.org/mailman/listinfo/kernel-build-reports