next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710)
next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20180710/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20180710/
Tree: next Branch: master Git Describe: next-20180710 Git Commit: 3951bd9fe3e2a1ca7e95fae2360c68402e663961 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 63 unique boards, 25 SoC families, 21 builds out of 200
Boot Regressions Detected:
arm:
multi_v7_defconfig: meson8b-odroidc1: lab-baylibre: failing since 55 days (last pass: next-20180515 - first fail: next-20180516)
multi_v7_defconfig+CONFIG_SMP=n: meson8b-odroidc1: lab-baylibre: new failure (last pass: next-20180706)
arm64:
defconfig: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)
defconfig+CONFIG_RANDOMIZE_BASE=y: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)
Boot Failures Detected:
arm:
multi_v7_defconfig+CONFIG_SMP=n meson8b-odroidc1: 1 failed lab
multi_v7_defconfig meson8b-odroidc1: 1 failed lab
arm64:
defconfig mt7622-rfb1: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y mt7622-rfb1: 1 failed lab
Offline Platforms:
arm:
imx_v6_v7_defconfig: imx7s-warp: 1 offline lab vf610-colibri-eval-v3: 1 offline lab
multi_v7_defconfig: imx7s-warp: 1 offline lab meson8b-odroidc1: 1 offline lab vf610-colibri-eval-v3: 1 offline lab
davinci_all_defconfig: da850-lcdk: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y: meson-gxbb-odroidc2: 1 offline lab meson-gxbb-p200: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-khadas-vim: 1 offline lab meson-gxl-s905x-nexbox-a95x: 1 offline lab meson-gxl-s905x-p212: 1 offline lab
defconfig: bcm2837-rpi-3-b: 1 offline lab meson-gxbb-odroidc2: 1 offline lab meson-gxbb-p200: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-khadas-vim: 1 offline lab meson-gxl-s905x-nexbox-a95x: 1 offline lab meson-gxl-s905x-p212: 1 offline lab meson-gxm-nexbox-a1: 1 offline lab rk3399-firefly: 1 offline lab sun50i-a64-pine64-plus: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y: bcm2837-rpi-3-b: 1 offline lab meson-gxbb-odroidc2: 1 offline lab meson-gxbb-p200: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-khadas-vim: 1 offline lab meson-gxl-s905x-nexbox-a95x: 1 offline lab meson-gxl-s905x-p212: 1 offline lab meson-gxm-nexbox-a1: 1 offline lab rk3399-firefly: 1 offline lab sun50i-a64-pine64-plus: 1 offline lab
--- For more info write to info@kernelci.org
On Tue, Jul 10, 2018 at 06:45:31AM -0700, kernelci.org bot wrote:
Today's linux-next fails to boot on mt7622-rfb1 with defconfig and defconfig+RANDOMIZE_BASE:
arm64:
defconfig: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)
defconfig+CONFIG_RANDOMIZE_BASE=y: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)
I'm not 100% sure if this is a lab failure or an early boot failure:
| Starting kernel ...
| [ATF][ 34.233534]save kernel info | [ATF][ 34.236565]Kernel_EL2 | [ATF][ 34.239322]Kernel is 64Bit | [ATF][ 34.242509]pc=0x40080000, r0=0x5cf48000, r1=0x0 | INFO: BL3-1: Preparing for EL3 exit to normal world, Kernel | INFO: BL3-1: Next image address = 0x40080000 | INFO: BL3-1: Next image spsr = 0x3c9 | [ATF][ 34.260778]el3_exit | ~$off | # PYBOOT: Exception: kernel: ERROR: did not start booting.
It only seems to affect this platform, other arm64 platforms seem fine. More details at:
https://kernelci.org/boot/id/5b44981a59b5141e5996baa1/
for the defconfig case, symptoms seem similar with RANDOMIZE_BASE.
Hi, Mark
thanks for reporting this issue.
I have fixed the issue in [1], which is caused by an update on pinctrl core and the driver doesn't have an immediate follow-up to the change.
Hi, Matthias
Could you help to add earlycon I posted in [2], which is helpful to identify at which point the boot is stuck instead of no any hint in the console?
[1] http://lists.infradead.org/pipermail/linux-mediatek/2018-July/014070.html
[2] http://lists.infradead.org/pipermail/linux-mediatek/2018-June/013709.html
On Tue, 2018-07-10 at 15:02 +0100, Mark Brown wrote:
On Tue, Jul 10, 2018 at 06:45:31AM -0700, kernelci.org bot wrote:
Today's linux-next fails to boot on mt7622-rfb1 with defconfig and defconfig+RANDOMIZE_BASE:
arm64:
defconfig: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)defconfig+CONFIG_RANDOMIZE_BASE=y: mt7622-rfb1: lab-baylibre-seattle: new failure (last pass: next-20180709)I'm not 100% sure if this is a lab failure or an early boot failure:
| Starting kernel ...
| [ATF][ 34.233534]save kernel info | [ATF][ 34.236565]Kernel_EL2 | [ATF][ 34.239322]Kernel is 64Bit | [ATF][ 34.242509]pc=0x40080000, r0=0x5cf48000, r1=0x0 | INFO: BL3-1: Preparing for EL3 exit to normal world, Kernel | INFO: BL3-1: Next image address = 0x40080000 | INFO: BL3-1: Next image spsr = 0x3c9 | [ATF][ 34.260778]el3_exit | ~$off | # PYBOOT: Exception: kernel: ERROR: did not start booting.
It only seems to affect this platform, other arm64 platforms seem fine. More details at:
https://kernelci.org/boot/id/5b44981a59b5141e5996baa1/
for the defconfig case, symptoms seem similar with RANDOMIZE_BASE. _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek
kernel-build-reports@lists.linaro.org
-
kernelci.org bot -
Mark Brown -
Sean Wang