All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Arnd Bergmann <arnd@arndb.de>,  <linux-kernel@vger.kernel.org>,
	<ath12k@lists.infradead.org>
Subject: Re: crosstool: x86 kernel compiled with GCC 14.1 fails to boot
Date: Tue, 09 Jul 2024 19:18:50 +0300	[thread overview]
Message-ID: <87le2abkt1.fsf@kernel.org> (raw)
In-Reply-To: <0e0150ca-fdfa-40cb-ad7f-6ac695b702e4@quicinc.com> (Jeff Johnson's message of "Tue, 9 Jul 2024 08:29:25 -0700")

Jeff Johnson <quic_jjohnson@quicinc.com> writes:

> On 7/8/2024 10:44 PM, Arnd Bergmann wrote:
>> On Tue, Jul 9, 2024, at 05:55, Jeff Johnson wrote:
>>> On 7/8/2024 6:57 PM, Jeff Johnson wrote:
>>>> 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.
>>>
>>> OK, with a bunch of debug turned off my image boots.
>>>
>>> Now to find the culprit.
>>>
>>> Current diff between original config and working config:
>> 
>> Nice! I've tried the reverse now, turning on the options
>> you have turned off on top of my defconfig. This version
>> still works for me, booting with a plain
>> 'qemu-system-x86_64 -kernel arch/x86_64/boot/bzImage'
>> and building with my arm64-to-x86 cross compiler.
>
> I picked my favorite to begin with, enabling KASAN (which in turn enabled a
> few others). The resulting kernel did not boot for me (just saw a black screen
> after the GRUB menu). Diff between working and non-working config is below.
>
> I then downloaded and built the config you supplied. With that I have the same
> behavior as my original config, the display is frozen with:
> Loading initial ramdisk ...
>
>
> [jjohnson:laptop 1966] diff .config.old .config

BTW there's also scripts/diffconfig which provides a prettier diff.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-07-09 16:19 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
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 [this message]
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=87le2abkt1.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.