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
Subject: Re: Can't boot kernel 6.17.4+ via rEFInd
Date: Tue, 28 Oct 2025 10:45:41 -0700 [thread overview]
Message-ID: <20251028174541.GA1548965@ax162> (raw)
In-Reply-To: <CAB95QARmr9b-jVdgDLpA4Qq=3WN7CYS46YEH4Ok4gpSdZHpq5A@mail.gmail.com>
On Mon, Oct 27, 2025 at 09:41:25PM +0100, Eugene Shalygin wrote:
> Hi Nathan,
>
> On Mon, 27 Oct 2025 at 20:35, Eugene Shalygin <eugene.shalygin@gmail.com> wrote:
> > Neither the patch nor 6.18-rc3 work. I'm going to try to revert
> > 5b5cdb1fe434e8adc97d5037e6d05dd386c4c4c6 together with anything that
> > is needed to apply the reversing patch.
>
> 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.
Could you post the output of 'readelf -S vmlinux vmlinux.unstripped'
from the broken and good builds? Does rEFInd have any sort of additional
debugging to see why/what it is complaining about not being able to
find?
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-28 17:45 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 [this message]
2025-10-29 20:07 ` Eugene Shalygin
2025-10-31 22:07 ` Nathan Chancellor
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=20251028174541.GA1548965@ax162 \
--to=nathan@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.