next/master boot: 296 boots: 62 failed, 230 passed with 4 conflicts (next-20171113)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171113/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171113/
Tree: next Branch: master Git Describe: next-20171113 Git Commit: c348a99ee55feac43b5b62a5957c6d8e2b6c3abe Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 52 unique boards, 17 SoC families, 33 builds out of 213
Boot Regressions Detected:
arm:
at91_dt_defconfig: at91sam9261ek: lab-free-electrons: new failure (last pass: next-20171110)
bcm2835_defconfig: bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110)
exynos_defconfig: exynos4412-odroidx2_rootfs:nfs: lab-collabora: failing since 5 days (last pass: next-20171107 - first fail: next-20171108) exynos5250-snow: lab-collabora: new failure (last pass: next-20171110) exynos5250-snow_rootfs:nfs: lab-collabora: failing since 4 days (last pass: next-20171108 - first fail: next-20171109)
imx_v4_v5_defconfig: imx27-phytec-phycard-s-rdk: lab-pengutronix: failing since 4 days (last pass: next-20171108 - first fail: next-20171109)
imx_v6_v7_defconfig: imx53-qsrb: lab-pengutronix: new failure (last pass: next-20171110) imx6q-nitrogen6x: lab-free-electrons: new failure (last pass: next-20171110) imx6ul-pico-hobbit: lab-pengutronix: new failure (last pass: next-20171110)
multi_v5_defconfig: at91sam9261ek: lab-free-electrons: new failure (last pass: next-20171110) imx27-phytec-phycard-s-rdk: lab-pengutronix: new failure (last pass: next-20171110)
multi_v7_defconfig: bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) sun5i-gr8-chip-pro: lab-free-electrons: new failure (last pass: next-20171110) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170921) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_ARM_LPAE=y: tegra124-jetson-tk1: lab-mhart: failing since 6 days (last pass: next-20171103 - first fail: next-20171107) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_EFI=y: bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170921) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y: tegra124-jetson-tk1: lab-mhart: failing since 6 days (last pass: next-20171103 - first fail: next-20171107) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_LKDTM=y: bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170920) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: armada-370-rd: lab-free-electrons: failing since 81 days (last pass: next-20170727 - first fail: next-20170824) armada-388-clearfog: lab-free-electrons: failing since 76 days (last pass: next-20170727 - first fail: next-20170828) at91-sama5d3_xplained: lab-free-electrons: failing since 349 days (last pass: next-20161111 - first fail: next-20161129) bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) imx6q-nitrogen6x: lab-free-electrons: failing since 80 days (last pass: next-20170727 - first fail: next-20170825) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170929) tegra124-jetson-tk1: lab-mhart: failing since 6 days (last pass: next-20171103 - first fail: next-20171107) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_SMP=n: armada-370-rd: lab-free-electrons: new failure (last pass: next-20171110) bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170908) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y: bcm2836-rpi-2-b: lab-collabora: new failure (last pass: next-20171110) exynos5800-peach-pi: lab-collabora: new failure (last pass: next-20171110) sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170929) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
multi_v7_defconfig+kselftest: exynos5250-snow: lab-collabora: new failure (last pass: next-20171110) exynos5422-odroidxu3: lab-collabora: new failure (last pass: next-20171108) exynos5800-peach-pi: lab-collabora: failing since 3 days (last pass: next-20171108 - first fail: next-20171110) tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
mvebu_v5_defconfig: kirkwood-openblocks_a7_rootfs:nfs: lab-free-electrons: failing since 160 days (last pass: next-20170323 - first fail: next-20170606)
omap2plus_defconfig: am335x-boneblack_rootfs:nfs: lab-collabora: failing since 5 days (last pass: next-20171107 - first fail: next-20171108)
sunxi_defconfig: sun5i-r8-chip: lab-free-electrons: new failure (last pass: next-20170921)
tegra_defconfig: tegra124-jetson-tk1_rootfs:nfs: lab-collabora: failing since 5 days (last pass: next-20171107 - first fail: next-20171108) tegra124-nyan-big: lab-collabora: failing since 5 days (last pass: next-20171107 - first fail: next-20171108)
arm64:
defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre: new failure (last pass: next-20171110)
defconfig+CONFIG_LKDTM=y: armada-3720-db: lab-free-electrons: failing since 104 days (last pass: next-20170728 - first fail: next-20170801)
x86:
defconfig+kselftest: x86-atom330: lab-mhart: failing since 4 days (last pass: next-20171108 - first fail: next-20171109)
Boot Failures Detected:
arm:
multi_v7_defconfig+kselftest exynos5250-snow: 1 failed lab exynos5422-odroidxu3: 1 failed lab exynos5800-peach-pi: 1 failed lab rk3288-rock2-square: 1 failed lab tegra124-nyan-big: 1 failed lab
multi_v7_defconfig+CONFIG_LKDTM=y bcm2836-rpi-2-b: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
mvebu_v5_defconfig kirkwood-openblocks_a7_rootfs:nfs: 1 failed lab
exynos_defconfig exynos4412-odroidx2_rootfs:nfs: 1 failed lab exynos5250-snow: 1 failed lab exynos5250-snow_rootfs:nfs: 1 failed lab
imx_v6_v7_defconfig imx53-qsrb: 1 failed lab imx6q-nitrogen6x: 1 failed lab imx6ul-pico-hobbit: 1 failed lab
multi_v7_defconfig bcm2836-rpi-2-b: 1 failed lab sun5i-gr8-chip-pro: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
omap2plus_defconfig am335x-boneblack_rootfs:nfs: 1 failed lab
multi_v7_defconfig+CONFIG_ARM_LPAE=y tegra124-nyan-big: 1 failed lab
sunxi_defconfig sun5i-r8-chip: 1 failed lab
multi_v5_defconfig at91sam9261ek: 1 failed lab imx27-phytec-phycard-s-rdk: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y tegra124-nyan-big: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y bcm2836-rpi-2-b: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n armada-370-rd: 1 failed lab bcm2836-rpi-2-b: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
bcm2835_defconfig bcm2836-rpi-2-b: 1 failed lab
multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y bcm2836-rpi-2-b: 1 failed lab exynos5800-peach-pi: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
tegra_defconfig tegra124-nyan-big: 1 failed lab
multi_v7_defconfig+CONFIG_PROVE_LOCKING=y armada-370-rd: 1 failed lab armada-388-clearfog: 1 failed lab armada-388-gp: 1 failed lab at91-sama5d3_xplained: 1 failed lab bcm2836-rpi-2-b: 1 failed lab imx6q-nitrogen6x: 1 failed lab rk3288-rock2-square: 1 failed lab sun5i-r8-chip: 1 failed lab tegra124-nyan-big: 1 failed lab
imx_v4_v5_defconfig imx27-phytec-phycard-s-rdk: 1 failed lab
at91_dt_defconfig at91sam9261ek: 1 failed lab
arm64:
defconfig+CONFIG_KASAN=y r8a7795-salvator-x: 1 failed lab
defconfig+kselftest apq8016-sbc: 1 failed lab bcm2837-rpi-3-b: 1 failed lab meson-gxl-s905x-khadas-vim: 1 failed lab
defconfig+CONFIG_LKDTM=y armada-3720-db: 1 failed lab r8a7795-salvator-x: 1 failed lab
defconfig meson-gxl-s905x-khadas-vim: 1 failed lab r8a7795-salvator-x: 1 failed lab
defconfig+CONFIG_EXPERT=y+CONFIG_ACPI=y r8a7795-salvator-x: 1 failed lab
defconfig+CONFIG_OF_UNITTEST=y r8a7795-salvator-x: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y r8a7795-salvator-x: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y r8a7795-salvator-x: 1 failed lab
x86:
defconfig+kselftest x86-atom330: 1 failed lab
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig+CONFIG_ARM_LPAE=y: tegra124-jetson-tk1: lab-mhart: FAIL lab-collabora: PASS
tegra_defconfig: tegra124-jetson-tk1_rootfs:nfs: lab-mhart: PASS lab-collabora: FAIL
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y: tegra124-jetson-tk1: lab-mhart: FAIL lab-collabora: PASS
multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: tegra124-jetson-tk1: lab-mhart: FAIL lab-collabora: PASS
--- For more info write to info@kernelci.org
On 13/11/17 19:02, kernelci.org bot wrote:
next/master boot: 296 boots: 62 failed, 230 passed with 4 conflicts (next-20171113)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171113/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171113/
Tree: next Branch: master Git Describe: next-20171113 Git Commit: c348a99ee55feac43b5b62a5957c6d8e2b6c3abe Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 52 unique boards, 17 SoC families, 33 builds out of 213
Boot Regressions Detected:
arm:
[...]
multi_v7_defconfig:
[...]
tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102 - first fail: next-20171103)
There are several things failing on the tegra124-nyan-big, at least I've isolated one with my latest bisection run:
6c78935777d12ead2d32adf3eb525a24faf02d04 is the first bad commit commit 6c78935777d12ead2d32adf3eb525a24faf02d04 Author: Kees Cook keescook@chromium.org Date: Fri Nov 10 16:34:52 2017 +0100
video: fbdev: Convert timers to use timer_setup()
These boot tests are with multi_v7_defconfig with CONFIG_MODULES and CONFIG_DRM_NOUVEAU disabled:
* the first one on the revision mentioned above, fails: https://lava.collabora.co.uk/scheduler/job/987651
* then the same but with the commit reverted, passes: https://lava.collabora.co.uk/scheduler/job/987652
This was found using the still experimental automated bisection tool for kernelci.org, I'm not sure yet how reliable the results are. I think the manual check with these 2 boots proves it, but I haven't really investigated further than that.
So I then did the same tests at the top of the branch, on the next-20171113 tag:
* next-20171113, fails but differently: https://lava.collabora.co.uk/scheduler/job/987653
* next-20171113 with the commit reverted, still fails: https://lava.collabora.co.uk/scheduler/job/987654
It's hard to tell whether the commit I mentioned got fixed in-between, I guess it would be best to not have any boot failure in any case.
The next thing I'll try is start a bisection for the other failure see on next-20171113 tag, with the commit above reverted and see if it leads anywhere...
Hope this helps!
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
On Tue, Nov 14, 2017 at 9:10 AM, Guillaume Tucker guillaume.tucker@collabora.com wrote:
On 13/11/17 19:02, kernelci.org bot wrote:
next/master boot: 296 boots: 62 failed, 230 passed with 4 conflicts (next-20171113)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171113/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171113/
Tree: next Branch: master Git Describe: next-20171113 Git Commit: c348a99ee55feac43b5b62a5957c6d8e2b6c3abe Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 52 unique boards, 17 SoC families, 33 builds out of 213
Boot Regressions Detected:
arm:
[...]
multi_v7_defconfig:[...]
tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102
- first fail: next-20171103)
There are several things failing on the tegra124-nyan-big, at least I've isolated one with my latest bisection run:
6c78935777d12ead2d32adf3eb525a24faf02d04 is the first bad commit commit 6c78935777d12ead2d32adf3eb525a24faf02d04 Author: Kees Cook keescook@chromium.org Date: Fri Nov 10 16:34:52 2017 +0100
video: fbdev: Convert timers to use timer_setup()These boot tests are with multi_v7_defconfig with CONFIG_MODULES and CONFIG_DRM_NOUVEAU disabled:
the first one on the revision mentioned above, fails: https://lava.collabora.co.uk/scheduler/job/987651
then the same but with the commit reverted, passes: https://lava.collabora.co.uk/scheduler/job/987652
This was found using the still experimental automated bisection tool for kernelci.org, I'm not sure yet how reliable the results are. I think the manual check with these 2 boots proves it, but I haven't really investigated further than that.
So I then did the same tests at the top of the branch, on the next-20171113 tag:
next-20171113, fails but differently: https://lava.collabora.co.uk/scheduler/job/987653
next-20171113 with the commit reverted, still fails: https://lava.collabora.co.uk/scheduler/job/987654
It's hard to tell whether the commit I mentioned got fixed in-between, I guess it would be best to not have any boot failure in any case.
The next thing I'll try is start a bisection for the other failure see on next-20171113 tag, with the commit above reverted and see if it leads anywhere...
Hope this helps!
Thanks for the report! I believe this is fixed with:
https://marc.info/?l=linux-fbdev&m=151056635200583&w=2
and that commit appears in next-20171114. Please let me know if that doesn't fix it, though!
-Kees
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
On 14/11/17 19:53, Kees Cook wrote:
On Tue, Nov 14, 2017 at 9:10 AM, Guillaume Tucker guillaume.tucker@collabora.com wrote:
On 13/11/17 19:02, kernelci.org bot wrote:
next/master boot: 296 boots: 62 failed, 230 passed with 4 conflicts (next-20171113)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171113/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171113/
Tree: next Branch: master Git Describe: next-20171113 Git Commit: c348a99ee55feac43b5b62a5957c6d8e2b6c3abe Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 52 unique boards, 17 SoC families, 33 builds out of 213
Boot Regressions Detected:
arm:
[...]
multi_v7_defconfig:[...]
tegra124-nyan-big: lab-collabora: failing since 9 days (last pass: next-20171102
- first fail: next-20171103)
There are several things failing on the tegra124-nyan-big, at least I've isolated one with my latest bisection run:
6c78935777d12ead2d32adf3eb525a24faf02d04 is the first bad commit commit 6c78935777d12ead2d32adf3eb525a24faf02d04 Author: Kees Cook keescook@chromium.org Date: Fri Nov 10 16:34:52 2017 +0100
video: fbdev: Convert timers to use timer_setup()These boot tests are with multi_v7_defconfig with CONFIG_MODULES and CONFIG_DRM_NOUVEAU disabled:
the first one on the revision mentioned above, fails: https://lava.collabora.co.uk/scheduler/job/987651
then the same but with the commit reverted, passes: https://lava.collabora.co.uk/scheduler/job/987652
This was found using the still experimental automated bisection tool for kernelci.org, I'm not sure yet how reliable the results are. I think the manual check with these 2 boots proves it, but I haven't really investigated further than that.
So I then did the same tests at the top of the branch, on the next-20171113 tag:
next-20171113, fails but differently: https://lava.collabora.co.uk/scheduler/job/987653
next-20171113 with the commit reverted, still fails: https://lava.collabora.co.uk/scheduler/job/987654
It's hard to tell whether the commit I mentioned got fixed in-between, I guess it would be best to not have any boot failure in any case.
The next thing I'll try is start a bisection for the other failure see on next-20171113 tag, with the commit above reverted and see if it leads anywhere...
Hope this helps!
Thanks for the report! I believe this is fixed with:
https://marc.info/?l=linux-fbdev&m=151056635200583&w=2
and that commit appears in next-20171114. Please let me know if that doesn't fix it, though!
Thanks, I've applied this patch in-place and confirmed it did fix the issue:
https://lava.collabora.co.uk/scheduler/job/988891
Will move on to next-20171114 now.
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
kernel-build-reports@lists.linaro.org
-
Guillaume Tucker -
Kees Cook -
kernelci.org bot