linux-kernel - Re: crosstool: x86 kernel compiled with GCC 14.1 fails to boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <917565ee-732a-4df0-a717-a71fbb34fd79@quicinc.com>
Date: Mon, 8 Jul 2024 18:57:18 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Kalle Valo <kvalo@...nel.org>, Arnd Bergmann <arnd@...db.de>
CC: <linux-kernel@...r.kernel.org>, <ath12k@...ts.infradead.org>
Subject: Re: crosstool: x86 kernel compiled with GCC 14.1 fails to boot

On 7/8/2024 11:16 AM, 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.

I had held off moving to 14.1 due to Kalle's issue as well as one other
internally-reported issue, but since a few others said they didn't have
issues, I thought I'd try it out for my laptop build in case it is just a
NUC-related issue.

And what I'm seeing after reboot and selecting the new image from GRUB is:
Loading Linux 6.10-rc6-wt-ath+ ...
Loading initial ramdisk ...

and that's it. It sits there with that on the display.

We tend to enable a lot of debug config options, so I'm wondering if one of
them is contributing to the issue? Guess I'll turn off a bunch of those
options and try again.

/jeff