From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
clang-built-linux <llvm@lists.linux.dev>,
Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: v6.14-12245-g91e5bfe317d8: Boot regression: rk3399-rock-pi-4b dragonboard-410c dragonboard-845c no console output
Date: Fri, 4 Apr 2025 17:27:57 -0700 [thread overview]
Message-ID: <20250405002757.GA836042@ax162> (raw)
In-Reply-To: <CA+G9fYtrsLHvMH=ofmdS3MMsMTEj3k0PD7=qsRsA4WkSqLkCzQ@mail.gmail.com>
On Thu, Apr 03, 2025 at 04:17:44PM +0530, Naresh Kamboju wrote:
> I’ve re-run the tests to validate the boot behavior on the Rock Pi 4 board
> with different Clang nightly versions and the latest mainline kernel.
>
> The combination using clang-nightly:20250319 successfully booted the
> Rock Pi 4 board.
> However, the combination using clang-nightly:20250401 failed to boot
> the same board.
>
> "name": "clang",
> "version": "21.0.0",
> "version_full": "Debian clang version 21.0.0
> (++20250401112529+290d7b82cb5d-1~exp1~20250401112547.1360)"
>
> Reference:
> - https://lkft.validation.linaro.org/scheduler/job/8196258
> - https://lkft.validation.linaro.org/scheduler/job/8196275
Thank you for verifying. Do you test with clang-20 and if so, are tests
at that same revision passing? I want to make sure this is an LLVM
regression before trying to get into figuring out how to bisect with
your setup. Another way to do that is to see if clang-nightly boots are
failing on the stable branches, which would point to Linux not being at
fault.
Cheers,
Nathan
next prev parent reply other threads:[~2025-04-05 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 12:49 v6.14-12245-g91e5bfe317d8: Boot regression: rk3399-rock-pi-4b dragonboard-410c dragonboard-845c no console output Naresh Kamboju
2025-04-03 1:18 ` Nathan Chancellor
2025-04-03 10:47 ` Naresh Kamboju
2025-04-05 0:27 ` Nathan Chancellor [this message]
2025-04-10 19:19 ` Naresh Kamboju
2025-04-12 1:45 ` Nathan Chancellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250405002757.GA836042@ax162 \
--to=nathan@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).