Processed: Re: Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 kmod does not work with XZ in-kernel module decompression Bug #1050586 [kmod] kmod is broken with custom kernels with CONFIG_MODULE_COMPRESS_*=y Bug #1050582 [kmod] kmod is broken with custom kernels with CONFIG_MODULE_COMPRESS_*=y Changed Bug title to

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Marco d'Itri
Control: retitle -1 kmod does not work with XZ in-kernel module decompression On Aug 27, Jon Westgate wrote: > Note that I already had "Support in-kernel module decompression" selected > when the compression method was XZ. > > Would you like me to try without it? No need to: we know that

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Jon Westgate
All, To confirm that switching to ZSTD works. I ran make menuconfig,    [*] Enable loadable module support  --->        Module compression mode (ZSTD) --->         [*]   Support in-kernel module decompression Note that I already had "Support in-kernel module decompression" selected

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Jon Westgate
Dear Marco and others, I will do a test build using ZSTD and see if that works. - I think the first thing I did was to switch back to XZ when this first happened Yesterday. I've been using XZ for module compression since it was available, I just select it using make menuconfig I'm not using

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Antonio
ticket: https://techpatterns.com/forums/about3040.html

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-27 Thread Antonio
I don't build kernel from source, I use binary packages installed from liquorix repositories https://liquorix.net/. I opened a ticket to their forum, maybe a recompilation of the kernel is enough. We await your reply... Il 27/08/23 03:10, Marco d'Itri ha scritto: On Aug 26, Jon Westgate

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Marco d'Itri
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > The error message it gave was "decompresson failed with status 6" Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with settings that are not supported by this XZ decoder". So it looks like you have compressed the modules (how?) with XZ

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Jon Westgate
Dear Marco, I'm using XZ if I turn off compression my initrd fails it's too big. Jon On 26/08/2023 22:25, Marco d'Itri wrote: On Aug 26, Jon Westgate wrote: Yes I am using compressed modules And are these modules compressed with xz or something else? This new code was introduced in the

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Marco d'Itri
On Aug 26, Jon Westgate wrote: > Yes I am using compressed modules And are these modules compressed with xz or something else? This new code was introduced in the latest snapshot, and apparently it fails when used with kernels with compressed modules support enabled (which so far is not the

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Jon Westgate
Yes I am using compressed modules On 26/08/2023 18:34, Marco d'Itri wrote: On Aug 26, Jon Westgate <0...@fsck.tv> wrote: The system partially booted but systemd then prevented boot due to missing modules, The error message it gave was "decompresson failed with status 6" Are you using

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Jon Westgate
CONFIG_MODULE_SIG=y # CONFIG_MODULE_SIG_FORCE is not set # CONFIG_MODULE_SIG_ALL is not set # CONFIG_MODULE_SIG_SHA1 is not set # CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y # CONFIG_MODULE_SIG_SHA384 is not set # CONFIG_MODULE_SIG_SHA512 is not set

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Marco d'Itri
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT) I see that you are using a custom kernel. What is the status of the CONFIG_MODULE_COMPRESS_* kernel configuration options? -- ciao, Marco signature.asc Description: PGP signature

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Marco d'Itri
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > The system partially booted but systemd then prevented boot due to missing > modules, > The error message it gave was "decompresson failed with status 6" Are you using compressed modules? -- ciao, Marco signature.asc Description: PGP signature

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

2023-08-26 Thread Jon Westgate
Package: kmod Version: 30+20230601-1 Severity: grave Justification: renders system unusable Dear Maintainer, I just did a normal apt upgrade and the following packages were upgraded: kmod 30+20230519-1 to 30-2.230601-1 libkmod2 30+20230519-1 to 30-2.230601-1 The system partially booted but