On Mon, 1 Jul 2024 at 17:42, Mark Brown broonie@kernel.org wrote:
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.
The boot test history shows that, GOOD: v6.10-rc5 BAD: v6.10-rc6
Other CI systems aren't showing this. I'm guessing you've updated the toolchain versions you're using and are running into:
Our LKFT tests saw the same bug as #31924.
BAD: "ar": "GNU ar (GNU Binutils for Debian) 2.42.50.20240625", "as": "GNU assembler (GNU Binutils for Debian) 2.42.50.20240625", "ld": "GNU ld (GNU Binutils for Debian) 2.42.50.20240625", "gcc": "gcc (Debian 13.3.0-1) 13.3.0",
Good: "ar": "GNU ar (GNU Binutils for Debian) 2.42", "as": "GNU assembler (GNU Binutils for Debian) 2.42", "ld": "GNU ld (GNU Binutils for Debian) 2.42", "gcc": "gcc (Debian 13.2.0-25) 13.2.0",
We are able to reproduce this bug ^. The gcc-13 builds failed and gcc-8 builds and clang-18 builds PASS.
and will see this with other kernels. It's probably worth testing toolchains before deploying them...
While we talk, I get to see today's Linux next and also encounter the same problem. Thanks for the suggestion to test toolchains.
- Naresh