next/master boot: 138 boots: 8 failed, 112 passed with 18 offline (next-20180619)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20180619/ Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20180619/
Tree: next Branch: master Git Describe: next-20180619 Git Commit: 42a0fd2e7b5f1c0130798e94285831d84035dbbf Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 59 unique boards, 23 SoC families, 19 builds out of 200
Boot Regressions Detected:
arm:
multi_v7_defconfig: sun4i-a10-cubieboard: lab-baylibre-seattle: failing since 60 days (last pass: next-20180419 - first fail: next-20180420) sun7i-a20-bananapi: lab-baylibre-seattle: failing since 60 days (last pass: next-20180419 - first fail: next-20180420) sun7i-a20-cubietruck: lab-baylibre-seattle: failing since 60 days (last pass: next-20180419 - first fail: next-20180420)
sunxi_defconfig: sun4i-a10-cubieboard: lab-baylibre-seattle: failing since 61 days (last pass: next-20180418 - first fail: next-20180419) sun7i-a20-bananapi: lab-baylibre-seattle: failing since 61 days (last pass: next-20180418 - first fail: next-20180419) sun7i-a20-cubietruck: lab-baylibre-seattle: failing since 61 days (last pass: next-20180418 - first fail: next-20180419)
arm64:
defconfig: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
defconfig+CONFIG_RANDOMIZE_BASE=y: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
Boot Failures Detected:
arm:
sunxi_defconfig sun4i-a10-cubieboard: 1 failed lab sun7i-a20-bananapi: 1 failed lab sun7i-a20-cubietruck: 1 failed lab
multi_v7_defconfig sun4i-a10-cubieboard: 1 failed lab sun7i-a20-bananapi: 1 failed lab sun7i-a20-cubietruck: 1 failed lab
arm64:
defconfig rk3399-firefly: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y rk3399-firefly: 1 failed lab
Offline Platforms:
arm:
sama5_defconfig: at91-sama5d4_xplained: 1 offline lab
multi_v7_defconfig: alpine-db: 1 offline lab at91-sama5d4_xplained: 1 offline lab meson8b-odroidc1: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab
tegra_defconfig: tegra124-jetson-tk1: 1 offline lab
sunxi_defconfig: sun5i-r8-chip: 1 offline lab
bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab
arm64:
defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab mt7622-rfb1: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab mt7622-rfb1: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab
--- For more info write to info@kernelci.org
On Tue, Jun 19, 2018 at 07:00:13AM -0700, kernelci.org bot wrote:
Today and yesterday's -next is failing to boot on rk3399-firefly in two configs:
defconfig: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
defconfig+CONFIG_RANDOMIZE_BASE=y: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)
The log ends with:
[ 2.629278] SWITCH_REG2: supplied by vcc3v3_sys [ 2.633030] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected! [ 2.633723] fan53555-reg: supplied by vcc_sys [ 2.6353|] Internal error: undefined instruction: 0 [#1] PREEMPT SMP
which is rather entertaining.
The pending fixes -next branch is fine. More diagnostics can be seen at:
https://kernelci.org/boot/id/5b28eadb59b514636d79a877/
(that's the defconfig.) Other boards don't seem to be affected, there's some other boards that are failing but don't seem to be related.
On 19/06/18 15:13, Mark Brown wrote:
On Tue, Jun 19, 2018 at 07:00:13AM -0700, kernelci.org bot wrote:
Today and yesterday's -next is failing to boot on rk3399-firefly in two configs:
defconfig: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)defconfig+CONFIG_RANDOMIZE_BASE=y: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)The log ends with:
[ 2.629278] SWITCH_REG2: supplied by vcc3v3_sys [ 2.633030] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected! [ 2.633723] fan53555-reg: supplied by vcc_sys [ 2.6353|] Internal error: undefined instruction: 0 [#1] PREEMPT SMP
which is rather entertaining.
Based on the logs from successful boots, I see it's CPUFreq that gets probed after fan53555-reg. I also see that it warns about unlisted OPPs in the successful boots. I guess, the undefined instruction could occur if there's issue with CPU DVFS(under voltage or frequency that's not supported). I don't have much knowledge on the platform, I am just guessing on the possible cause here.
On Tue, Jun 19, 2018 at 03:22:47PM +0100, Sudeep Holla wrote:
Based on the logs from successful boots, I see it's CPUFreq that gets probed after fan53555-reg. I also see that it warns about unlisted OPPs in the successful boots. I guess, the undefined instruction could occur if there's issue with CPU DVFS(under voltage or frequency that's not supported). I don't have much knowledge on the platform, I am just guessing on the possible cause here.
Yeah, that was my guess - either an out of spec voltage/frequency was selected or the regulator isn't able to keep up with the voltage transition or a load spike and the power browns out.
On Tue, Jun 19, 2018 at 07:00:13AM -0700, kernelci.org bot wrote:
Today and yesterday's -next is failing to boot on rk3399-firefly in two
configs:
defconfig: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)>> defconfig+CONFIG_RANDOMIZE_BASE=y: rk3399-firefly: lab-baylibre-seattle: failing since 1 day (last pass: next-20180615 - first fail: next-20180618)>The log ends with:
[ 2.629278] SWITCH_REG2: supplied by vcc3v3_sys [ 2.633030] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected! [ 2.633723] fan53555-reg: supplied by vcc_sys [ 2.6353|] Internal error: undefined instruction: 0 [#1] PREEMPT SMP
which is rather entertaining.
Am Dienstag, 19. Juni 2018, 16:41:43 CEST schrieb Mark Brown: On Tue, Jun 19, 2018 at 03:22:47PM +0100, Sudeep Holla wrote:
Based on the logs from successful boots, I see it's CPUFreq that gets probed after fan53555-reg. I also see that it warns about unlisted OPPs in the successful boots. I guess, the undefined instruction could occur if there's issue with CPU DVFS(under voltage or frequency that's not supported). I don't have much knowledge on the platform, I am just guessing on the possible cause here.
Yeah, that was my guess - either an out of spec voltage/frequency was selected or the regulator isn't able to keep up with the voltage transition or a load spike and the power browns out.
I guess this is related to arm64: dts: rockchip: correct voltage selector Firefly-RK3399 [0]
which is in so far interesting as the patch seems to fix a similar issue to the above with the opposite "fcs,suspend-voltage-selector" value. And also claims to be in line with the vendor kernel.
From looking at the schematics, we might have a discrepancy between the
fcs,suspend-voltage-selector and vsel input-pin leading to a gpio [likely depending on what the bootloader set this pin up for].
I'll drop the patch for now and get in contact with the patch submitter.
Heiko
kernel-build-reports@lists.linaro.org
-
Heiko Stübner -
kernelci.org bot -
Mark Brown -
Sudeep Holla