mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>, Arnd Bergmann <arnd@arndb.de>
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, 8 Jul 2024 18:57:18 -0700	[thread overview]
Message-ID: <917565ee-732a-4df0-a717-a71fbb34fd79@quicinc.com> (raw)
In-Reply-To: <87y16bbvgb.fsf@kernel.org>

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



  parent reply	other threads:[~2024-07-09  1:57 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
2024-07-08 21:39   ` Genes Lists
2024-07-09  1:57 ` Jeff Johnson [this message]
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=917565ee-732a-4df0-a717-a71fbb34fd79@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=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