arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
Full Boot Summary: https://kernelci.org/boot/all/job/arm-soc/kernel/v4.7-rc3-216-gec0776a212c1/ Full Build Summary: https://kernelci.org/build/arm-soc/kernel/v4.7-rc3-216-gec0776a212c1/
Tree: arm-soc Branch: local/for-next Git Describe: v4.7-rc3-216-gec0776a212c1 Git Commit: ec0776a212c150f2b5e59c23eb924b7465e41218 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git Tested: 106 unique boards, 25 SoC families, 38 builds out of 143
Boot Failures Detected: https://kernelci.org/boot/?v4.7-rc3-216-gec0776a212c1&fail
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
Offline Platforms:
arm:
multi_v7_defconfig+CONFIG_EFI=y: hip04-d01: 1 offline lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y: hip04-d01: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig+CONFIG_SMP=n: imx6q-sabrelite: lab-collabora: FAIL lab-embeddedbits: PASS
--- For more info write to info@kernelci.org
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.
Arnd
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 labThese 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.
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 labThese 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
Arnd Bergmann arnd@arndb.de writes:
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 labThese all seem to have broken after yesterday's merges, adding Alexandre and Krzysztof to Cc here so they can have a look.
The exynos5410 fails look like the UART3 issue reported earlier and which is also happening in linux-next.
Krzysztof posted a fix[1] that was tested by Javier and myself that fixed the problem, but I don't see that upstream yet.
Krzysztof: did you get that fix submitted yet?
Kevin
On Wed, Jun 15, 2016 at 11:07:50AM -0700, Kevin Hilman wrote:
Arnd Bergmann arnd@arndb.de writes:
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 labThese all seem to have broken after yesterday's merges, adding Alexandre and Krzysztof to Cc here so they can have a look.
The exynos5410 fails look like the UART3 issue reported earlier and which is also happening in linux-next.
Krzysztof posted a fix[1] that was tested by Javier and myself that fixed the problem, but I don't see that upstream yet.
Krzysztof: did you get that fix submitted yet?
Kevin
The v2 of it is here: https://patchwork.kernel.org/patch/9144897/
I do not recall receiving any feedback nor confirmation of applying the patch. I guess it is time to resend. I'll do it on Thursday.
Best regards, Krzysztof
Krzysztof Kozlowski k.kozlowski@samsung.com writes:
On Wed, Jun 15, 2016 at 11:07:50AM -0700, Kevin Hilman wrote:
Arnd Bergmann arnd@arndb.de writes:
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 labThese all seem to have broken after yesterday's merges, adding Alexandre and Krzysztof to Cc here so they can have a look.
The exynos5410 fails look like the UART3 issue reported earlier and which is also happening in linux-next.
Krzysztof posted a fix[1] that was tested by Javier and myself that fixed the problem, but I don't see that upstream yet.
Krzysztof: did you get that fix submitted yet?
Kevin
The v2 of it is here: https://patchwork.kernel.org/patch/9144897/
oops, yeah. That's the one Javier and I tested.
I do not recall receiving any feedback nor confirmation of applying the patch. I guess it is time to resend. I'll do it on Thursday.
Yeah, add the tested-by, and since this fixes a known regression, I guess it should go in unless there are any objections.
Kevin
kernel-build-reports@lists.linaro.org
-
Alexandre Belloni -
Arnd Bergmann -
kernelci.org bot -
Kevin Hilman -
Krzysztof Kozlowski