From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: linux-modules@vger.kernel.org
Subject: Unbootable system with kmod-31
Date: Tue, 3 Oct 2023 16:55:10 -0400 [thread overview]
Message-ID: <acf37f00-cea3-4f77-9c05-3c0301221d2a@moonlit-rail.com> (raw)
[ Resend due to HTML not making it through ]
Hello Lucas, et al,
I upgraded from kmod-30 to kmod-31, and could not boot due to an
inability to load any module. Any invocation of insmod bombs with,
"decompression failed with status 6". I strace'd the issue to the
call to finit_module(). In kmod 30, the call to init_module()
works fine.
All modules are xz-compressed, for which support is present in the
kernel (using mainline kernel 6.5 here).
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_KERNEL_XZ=y
CONFIG_MODULE_COMPRESS_XZ=y
CONFIG_FW_LOADER_COMPRESS_XZ=y
CONFIG_XZ_DEC=y
However, on a whim, I tried "make nconfig", searched for any
kernel config options containing "XZ", and at the top of the list:
# CONFIG_DECOMPRESS_XZ is not set
That appears to be an automatically-set option triggered by the
presence of initrd; but:
# CONFIG_BLK_DEV_INITRD is not set
I don't know if (de)compression on an initrd is related to same
on a module, but it was the only thing I could find where XZ was
not =Y.
Kris
next reply other threads:[~2023-10-03 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:55 Kris Karas (Bug Reporting) [this message]
2023-10-03 21:08 ` Unbootable system with kmod-31 Marco d'Itri
2023-10-03 23:37 ` Lucas De Marchi
2023-10-04 1:02 ` Kris Karas (Bug Reporting)
2023-10-04 2:44 ` Lucas De Marchi
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=acf37f00-cea3-4f77-9c05-3c0301221d2a@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=linux-modules@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).