Re: arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)

On Wednesday, June 15, 2016 11:18:06 AM CEST Alexandre Belloni wrote:

On 15/06/2016 at 11:10:29 +0200, Arnd Bergmann wrote :

...

On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:

...

arm:

multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
    exynos5410-odroidxu: 1 failed lab

multi_v7_defconfig+CONFIG_LKDTM=y:
    exynos5410-odroidxu: 1 failed lab

multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
    exynos5410-odroidxu: 1 failed lab

multi_v7_defconfig+CONFIG_EFI=y:
    exynos5410-odroidxu: 1 failed lab

exynos_defconfig:
    exynos5410-odroidxu: 1 failed lab

multi_v7_defconfig+CONFIG_ARM_LPAE=y:
    exynos5410-odroidxu: 1 failed lab

multi_v7_defconfig:
    exynos5410-odroidxu: 1 failed lab

multi_v5_defconfig:
    at91sam9261ek: 1 failed lab
    at91sam9m10g45ek: 1 failed lab
    at91sam9x25ek: 1 failed lab
    at91sam9x35ek: 1 failed lab

These all seem to have broken after yesterday's merges, adding Alexandre and Krzysztof to Cc here so they can have a look.

Well, multi_v5 is not broken, this is an issue with the lab setup that is being solved right now. As for multi_v7, as the 8250 driver is included in multi_v5, the Atmel UARTs are called ttyATx instead of ttySx. Until now, "console=ttyS0,115200" was passed to the kernel, hence no output was present on the UART but the boards are booting fine.

Ok, thanks for having a look!

Arnd