[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <145b39a0-da05-4c60-a019-c1a6211e6c77@sirena.org.uk>
Date: Mon, 1 Jul 2024 13:12:07 +0100
From: Mark Brown <broonie@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.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, 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:
https://sourceware.org/bugzilla/show_bug.cgi?id=31924#c9
and will see this with other kernels. It's probably worth testing
toolchains before deploying them...
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists