From: Nathan Chancellor <nathan@kernel.org>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: Can't boot kernel 6.17.4+ via rEFInd
Date: Fri, 31 Oct 2025 18:07:32 -0400 [thread overview]
Message-ID: <20251031220732.GA2254630@ax162> (raw)
In-Reply-To: <CAB95QARtzDWensRzui3d-7+jhymcFBOBi78ev9LMy=ZFJMDCTA@mail.gmail.com>
Hi Eugene,
On Wed, Oct 29, 2025 at 09:07:20PM +0100, Eugene Shalygin wrote:
> On Tue, 28 Oct 2025 at 18:45, Nathan Chancellor <nathan@kernel.org> wrote:
> > > Replacing CONFIG_KERNEL_ZSTD with CONFIG_KERNEL_GZIP made the kernel
> > > bootable. What does that mean?
> >
> > Hmmmm, I am not sure... That seems rather odd within the context of the
> > flagged change.
>
> Huh! The fourth of my machines with the similar config (also fully
> updated ~amd64 Gentoo) with rEFind boots kernel 6.17.5 with
> CONFIG_KERNEL_ZSTD enabled.
>
> > Could you post the output of 'readelf -S vmlinux vmlinux.unstripped'
> > from the broken and good builds?
>
> Attached.
Unfortunately, nothing appears to be out of the ordinary there... Only
.modinfo gets removed from the vmlinux.unstripped to vmlinux stage.
> > Does rEFInd have any sort of additional
> > debugging to see why/what it is complaining about not being able to
> > find?
>
> No, unfortunately. However, I was unable to find the first part of the
> error message ("Not Found") in the rEFInd sources.
I am guessing the "Not Found" is EFI_NOT_FOUND, so I think this is
coming from StartEFIImage() in refind/launch_efi.c:
https://sourceforge.net/p/refind/code/ci/253abe5c4af58d044912517daa567c4440612c46/tree/refind/launch_efi.c#l290
I am not sure where the LoadImage call comes from (the firmware?) so I
don't really know why that call would fail... Has CONFIG_KERNEL_ZSTD
always worked in this configuration? Presumably since you are not seeing
"Invalid loader file", you are going into the
if ((LoaderType == LOADER_TYPE_EFI) || (LoaderType == LOADER_TYPE_GZIP)) {
branch there. I am at a bit of a loss here. Ard, could you see any
obvious reason from an EFI perspective why
3e86e4d74c04 ("kbuild: keep .modinfo section in vmlinux.unstripped")
would cause issues with booting via rEFInd? You can see Eugene's
original report at
https://lore.kernel.org/CAB95QARfqSUNJCCgyPcTPu0-hk10e-sOVVMrnpKd6OdV_PHrGA@mail.gmail.com/
and subsequent replies in case they are relevant.
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-31 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 8:25 Can't boot kernel 6.17.4+ via rEFInd Eugene Shalygin
2025-10-26 21:13 ` Nathan Chancellor
2025-10-27 19:35 ` Eugene Shalygin
2025-10-27 20:41 ` Eugene Shalygin
2025-10-28 17:45 ` Nathan Chancellor
2025-10-29 20:07 ` Eugene Shalygin
2025-10-31 22:07 ` Nathan Chancellor [this message]
2025-11-01 9:28 ` Eugene Shalygin
2025-11-03 15:00 ` Ard Biesheuvel
2025-11-03 21:22 ` Eugene Shalygin
2025-11-03 21:28 ` Ard Biesheuvel
2025-11-04 15:04 ` Eugene Shalygin
2025-11-08 9:06 ` Eugene Shalygin
2026-03-07 8:08 ` Nathan Chancellor
2026-03-08 17:59 ` Eugene Shalygin
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=20251031220732.GA2254630@ax162 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=eugene.shalygin@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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 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.