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

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

[Mark Brown]

[-- 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
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

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

[Sean Wang]

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