Mainline: v6.10-rc6 boot failed across all arm64 devices

[Will Deacon]

Hi Naresh,

This report is quite hard to follow, so just some minor comments which
you can hopefully take on board to improve things in future:

On Mon, Jul 01, 2024 at 05:28:29PM +0530, Naresh Kamboju wrote:
> The mainline kernel v6.10-rc6 boot failed across all arm64 devices and
> qemu-arm64 and no crash log found (earlycon) did not help.
> 
> But the defconfig builds boot PASS.
> 
> The boot problem is with defconfig + Extra Kconfigs and builds links
> provided in the bottom of this email.

If I go to the bottom of the email, I see this:

> Links:
> -----
>  - https://storage.tuxsuite.com/public/linaro/lkft/builds/2idWrbdtwMqpD9wx7IPRGJ7Dsx3/
>  - https://storage.tuxsuite.com/public/linaro/lkft/builds/2idWrYDposdlRsS4jwF916a0qGE/
>  - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.10-rc6/testrun/24473346/suite/boot/test/gcc-13-lkftconfig-libgpiod/history/
>  - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.10-rc6/testrun/24473903/suite/boot/test/gcc-13-lkftconfig-rcutorture/history/

but these are just random links without any context. The first two appear
to be kernel build artifacts, but I can't tell:

  - Are both "good" or "bad"?
  - What is the difference between them?

If I look at the first of the last two links, click through to the
"qemu-arm64" target and follow the "job_url" link, then I end up at:

  https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2idWuAb51mcz7lO1BAj8Aw0BrNY

which has some empty logs and something from "TuxRun" which says:

  {"error": "File not found"}

It's very hard to know what to do with this :/

Will