[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYs+RfnttPg7E_TAGW4sgnLOuvUQnZj6kHsXeRy=JEMOcg@mail.gmail.com>
Date: Mon, 1 Jul 2024 19:04:09 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>, Catalin Marinas <catalin.marinas@....com>,
Mark Rutland <mark.rutland@....com>, Aishwarya TCV <Aishwarya.TCV@....com>,
Arnd Bergmann <arnd@...db.de>, Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: Mainline: v6.10-rc6 boot failed across all arm64 devices
On Mon, 1 Jul 2024 at 17:42, Mark Brown <broonie@...nel.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",
> https://sourceware.org/bugzilla/show_bug.cgi?id=31924#c9
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
Powered by blists - more mailing lists