From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kalle Valo" <kvalo@kernel.org>
Cc: linux-kernel@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: crosstool: x86 kernel compiled with GCC 14.1 fails to boot
Date: Mon, 08 Jul 2024 21:03:22 +0200 [thread overview]
Message-ID: <0ddafa32-1fc2-45e1-b71c-beb64f8cd589@app.fastmail.com> (raw)
In-Reply-To: <87y16bbvgb.fsf@kernel.org>
On Mon, Jul 8, 2024, at 20:16, Kalle Valo wrote:
> Hi Arnd,
>
> I installed GCC 14.1 from:
>
> https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/14.1.0/
>
> But I have a problem that a kernel compiled with that compiler fails to
> boot on my x86 NUC test box. I don't see any errors, just black screen
> and I assume after that the kernel either crashes or reboots and goes to
> back to the GRUB menu. This loop seems to continue forever. GCC 13.2 and
> older from crosstool work just fine.
>
> Do you happen to have any ideas what could cause this or how to debug
> further?
Thanks for the report. Unfortunately I have no idea what the
problem may be, and so far nobody else has reported this.
For debugging, what I'd try first is to run the same kernel in
qemu to see if that works, or attach gdb and step through the
early boot if it doesn't.
I have tried reproducing it, but with my arm64 hosted x86-64
cross-compiler, it boots a defconfig x86-64 kernel in qemu just
fine.
Arnd
next prev parent reply other threads:[~2024-07-08 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 18:16 crosstool: x86 kernel compiled with GCC 14.1 fails to boot Kalle Valo
2024-07-08 19:03 ` Arnd Bergmann [this message]
2024-07-08 21:39 ` Genes Lists
2024-07-09 1:57 ` Jeff Johnson
2024-07-09 3:55 ` Jeff Johnson
2024-07-09 5:44 ` Arnd Bergmann
2024-07-09 15:29 ` Jeff Johnson
2024-07-09 16:18 ` Kalle Valo
2024-07-09 19:33 ` Arnd Bergmann
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=0ddafa32-1fc2-45e1-b71c-beb64f8cd589@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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