next/master boot: 148 boots: 10 failed, 136 passed with 2 untried/unknown (next-20200129)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200129/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200129/
Tree: next Branch: master Git Describe: next-20200129 Git Commit: 335e1cb5b8c0f961767537c3bb8db47b8fcb5671 Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 63 unique boards, 15 SoC families, 17 builds out of 198
Boot Regressions Detected:
arm:
exynos_defconfig: gcc-8: exynos4412-odroidx2: lab-collabora: new failure (last pass: next-20200122)
multi_v7_defconfig+CONFIG_SMP=n: gcc-8: exynos4412-odroidx2: lab-collabora: new failure (last pass: next-20200122) exynos5422-odroidxu3: lab-collabora: new failure (last pass: next-20200122)
arm64:
defconfig: gcc-8: apq8096-db820c: lab-bjorn: new failure (last pass: next-20200123)
defconfig+CONFIG_CPU_BIG_ENDIAN=y: gcc-8: meson-gxl-s805x-p241: lab-baylibre: new failure (last pass: next-20200123)
defconfig+CONFIG_RANDOMIZE_BASE=y: gcc-8: hip07-d05: lab-collabora: new failure (last pass: next-20200122)
x86_64:
x86_64_defconfig: gcc-8: qemu_x86_64: lab-baylibre: new failure (last pass: next-20200123)
x86_64_defconfig+kvm_guest: gcc-8: qemu_x86_64: lab-baylibre: new failure (last pass: next-20200123)
Boot Failures Detected:
arm: multi_v7_defconfig: gcc-8: bcm2836-rpi-2-b: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n: gcc-8: exynos4412-odroidx2: 1 failed lab exynos5422-odroidxu3: 1 failed lab
exynos_defconfig: gcc-8: exynos4412-odroidx2: 1 failed lab exynos5422-odroidxu3: 1 failed lab
arm64: defconfig+CONFIG_RANDOMIZE_BASE=y: gcc-8: meson-gxm-q200: 1 failed lab
defconfig: gcc-8: apq8096-db820c: 1 failed lab msm8998-mtp: 1 failed lab
x86_64: x86_64_defconfig: gcc-8: qemu_x86_64: 1 failed lab
x86_64_defconfig+kvm_guest: gcc-8: qemu_x86_64: 1 failed lab
--- For more info write to info@kernelci.org
On Wed, Jan 29, 2020 at 07:54:18AM -0800, kernelci.org bot wrote:
Today's -next fails to boot on Odroid X2 and XU3 with exynos_defconfig or multi_v7_defconfig with SMP=n. It appears to get stuck in a loop probing the I2S secondary DAI for some reason:
12:07:05.997409 <6>[ 6.421596] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 666000 KHz) 12:07:05.997653 <4>[ 6.429763] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s 12:07:06.006838 <4>[ 6.439652] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s 12:07:06.015764 <4>[ 6.448666] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
and so on ad infinitum. Vanilla multi_v7_defconfig is fine and just displays a saingle copy of that log message. Full logs and other details here:
https://kernelci.org/boot/id/5e3176467f121dbdef2824fc/ https://kernelci.org/boot/id/5e317b7322dcdaa3e5282500/ https://kernelci.org/boot/id/5e317c0f6bfd765fb42824f1/ https://kernelci.org/boot/id/5e317517be8559c7542824f1/
I don't *think* it's an audio issue as mainline seems fine and all the ASoC changes have already landed in mainline for this merge window.
On Wed, Jan 29, 2020 at 04:11:13PM +0000, Mark Brown wrote:
On Wed, Jan 29, 2020 at 07:54:18AM -0800, kernelci.org bot wrote:
Today's -next fails to boot on Odroid X2 and XU3 with exynos_defconfig or multi_v7_defconfig with SMP=n. It appears to get stuck in a loop probing the I2S secondary DAI for some reason:
12:07:05.997409 <6>[ 6.421596] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 666000 KHz) 12:07:05.997653 <4>[ 6.429763] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s 12:07:06.006838 <4>[ 6.439652] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s 12:07:06.015764 <4>[ 6.448666] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
and so on ad infinitum. Vanilla multi_v7_defconfig is fine and just displays a saingle copy of that log message. Full logs and other details here:
https://kernelci.org/boot/id/5e3176467f121dbdef2824fc/ https://kernelci.org/boot/id/5e317b7322dcdaa3e5282500/ https://kernelci.org/boot/id/5e317c0f6bfd765fb42824f1/ https://kernelci.org/boot/id/5e317517be8559c7542824f1/
I don't *think* it's an audio issue as mainline seems fine and all the ASoC changes have already landed in mainline for this merge window.
Thanks for the report.
Marek spotted it as well and sent a patch
Best regards, Krzysztof
kernel-build-reports@lists.linaro.org