Re: next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710)

Mark Brown
2018-07-10T14:02:13Z

[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]

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.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org