Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Hi, On Sat, 6 Sep 2025 14:37:30 +0200 Salvatore Bonaccorso wrote: If you might not need firmware-nvidia-graphics, then removing it might be an option an regenerating the initramfs. It seems I indeed don't need it, so removing it solved *my* particular part of this problem, my /boot is now 67% with three kernels installed. I'm not closing this bug because of the Bens message #29. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
On Sat, 6 Sep 2025 14:37:30 +0200 Salvatore Bonaccorso wrote: > Hi Paul, > > On Sat, Sep 06, 2025 at 02:06:37PM +0200, Paul Gevers wrote: > > Hi, > > > > On 06-09-2025 11:42, Salvatore Bonaccorso wrote: > > > Can you please with lsinitramfs list the contents for both and provide > > > those for comparison? > > > > > > Please find those attached. > > I had a look, unfortunately I think this is then expected. The > majority of changes are from the firmware-nvidia-graphics package, and > the package itself increased from 20250410-2 to 20250808-1 > substantially due to more firmare added: > > $ dpkg-deb -f firmware-nvidia-graphics_20250410-2_all.deb Installed- Size > 64591 > $ dpkg-deb -f firmware-nvidia-graphics_20250808-1_all.deb Installed- Size > 156283 > > For instance the added > usr/lib/firmware/nvidia/tu102/gsp/gsp-570.144.bin is 28M in size. > Attached the diff I generated with some pre-subistitution for easier > comparision. The huge size and growing number of different builds of the Nvidia GSP firmware are a real problem. I don't think there's anything that we can do about that in the firmware package. However: 1. This is exacerbated by the fact that the nouveau driver declares multiple versions of the GSP firmware for some chips with MODULE_FIRMWARE(), but only needs one (per chip). In the short term I think we should patch nouveau to remove the MODULE_FIRMWARE() declarations for v535.113.01 for chips where it prefers v570.144. 2. In the medium term we need to move to using generic framebuffer drivers in the initramfs, but several packages have to be changed to make that work. Ben. > If you might not need firmware-nvidia-graphics, then removing it might > be an option an regenerating the initramfs. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Hi, On 06-09-2025 11:42, Salvatore Bonaccorso wrote: Can you please with lsinitramfs list the contents for both and provide those for comparison? Please find those attached. Paul initrd.img-6.12.38+deb13-amd64.lsinitramfs.xz Description: application/xz initrd.img-6.16.3+deb14-amd64.lsinitramfs.xz Description: application/xz OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Control: tags -1 + moreinfo Hi Paul, On Sat, Aug 30, 2025 at 05:48:48PM +0200, Paul Gevers wrote: > Source: linux > Version: 6.16.3-1 > Severity: normal > > Hi, > > Not sure if this is actionable and indeed beyond expectations, but just in > case this points at a problem in the packaging. Feel free to close if I just > need to deal with this. > > I just upgraded my forky system and the upgrade failed: > update-initramfs: Generating /boot/initrd.img-6.16.3+deb14-amd64 > zstd: error 70 : Write error : cannot write block : No space left on device > E: mkinitramfs failure zstd -q -9 -T0 70 > update-initramfs: failed for /boot/initrd.img-6.16.3+deb14-amd64 with 1. > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 > dpkg: error processing package linux-image-6.16.3+deb14-amd64 (--configure): > installed linux-image-6.16.3+deb14-amd64 package post-installation script > subprocess returned error exit status 1 > Setting up linux-libc-dev (6.16.3-1) ... > dpkg: dependency problems prevent configuration of linux-image-amd64: > linux-image-amd64 depends on linux-image-6.16.3+deb14-amd64 (= 6.16.3-1); > however: > Package linux-image-6.16.3+deb14-amd64 is not configured yet. > > dpkg: error processing package linux-image-amd64 (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > linux-image-6.16.3+deb14-amd64 > linux-image-amd64 > Error: Sub-process /usr/bin/dpkg returned an error code (1) > > > I don't have a big /boot system, as the default boot partition used to be > (way too) small. I recall that I once enable something to only install > required modules into the initrd, which helped me along until today. > > /boot right after upgrade: > paul@toba ~ $ df -h /boot > Filesystem Size Used Avail Use% Mounted on > /dev/nvme0n1p2 456M 281M 151M 66% /boot > paul@toba ~ $ ls -al /boot/ > total 273416 > drwxr-xr-x 5 root root 1024 Aug 30 17:32 . > drwxr-xr-x 18 root root 4096 Aug 30 17:31 .. > -rw-r--r-- 1 root root283225 Jul 3 21:01 config-6.12.35+deb13-amd64 > -rw-r--r-- 1 root root283270 Jul 16 09:13 config-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root289665 Aug 24 23:29 config-6.16.3+deb14-amd64 > drwx-- 3 root root 4096 Jan 1 1970 efi > drwxr-xr-x 5 root root 1024 Aug 20 18:36 grub > -rw-r--r-- 1 root root 120238850 Jul 22 19:33 > initrd.img-6.12.35+deb13-amd64 > -rw-r--r-- 1 root root 120394731 Aug 30 08:39 > initrd.img-6.12.38+deb13-amd64 > drwx-- 2 root root 12288 Nov 17 2024 lost+found > -rw-r--r-- 1 root root83 Jul 3 21:01 > System.map-6.12.35+deb13-amd64 > -rw-r--r-- 1 root root83 Jul 16 09:13 > System.map-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root92 Aug 24 23:29 System.map-6.16.3+deb14-amd64 > -rw-r--r-- 1 root root 12093376 Jul 3 21:01 vmlinuz-6.12.35+deb13-amd64 > -rw-r--r-- 1 root root 12097472 Jul 16 09:13 vmlinuz-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root 13162432 Aug 24 23:29 vmlinuz-6.16.3+deb14-amd64 > > /boot after $(sudo apt remove linux-image-6.12.35+deb13-amd64): > paul@toba ~ $ df -h /boot > Filesystem Size Used Avail Use% Mounted on > /dev/nvme0n1p2 456M 337M 95M 79% /boot > paul@toba ~ $ ls -al /boot/ > total 330986 > drwxr-xr-x 5 root root 1024 Aug 30 17:36 . > drwxr-xr-x 18 root root 4096 Aug 30 17:35 .. > -rw-r--r-- 1 root root283270 Jul 16 09:13 config-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root289665 Aug 24 23:29 config-6.16.3+deb14-amd64 > drwx-- 3 root root 4096 Jan 1 1970 efi > drwxr-xr-x 5 root root 1024 Aug 30 17:36 grub > -rw-r--r-- 1 root root 120394731 Aug 30 08:39 > initrd.img-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root 191341702 Aug 30 17:36 initrd.img-6.16.3+deb14-amd64 > drwx-- 2 root root 12288 Nov 17 2024 lost+found > -rw-r--r-- 1 root root83 Jul 16 09:13 > System.map-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root92 Aug 24 23:29 System.map-6.16.3+deb14-amd64 > -rw-r--r-- 1 root root 12097472 Jul 16 09:13 vmlinuz-6.12.38+deb13-amd64 > -rw-r--r-- 1 root root 13162432 Aug 24 23:29 vmlinuz-6.16.3+deb14-amd64 > > Note the increase from 120394731 to 191341702 for the initrd. Can you please with lsinitramfs list the contents for both and provide those for comparison? Regards, Salvatore
Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Hi Paul, On Sat, Sep 06, 2025 at 02:06:37PM +0200, Paul Gevers wrote: > Hi, > > On 06-09-2025 11:42, Salvatore Bonaccorso wrote: > > Can you please with lsinitramfs list the contents for both and provide > > those for comparison? > > > Please find those attached. I had a look, unfortunately I think this is then expected. The majority of changes are from the firmware-nvidia-graphics package, and the package itself increased from 20250410-2 to 20250808-1 substantially due to more firmare added: $ dpkg-deb -f firmware-nvidia-graphics_20250410-2_all.deb Installed-Size 64591 $ dpkg-deb -f firmware-nvidia-graphics_20250808-1_all.deb Installed-Size 156283 For instance the added usr/lib/firmware/nvidia/tu102/gsp/gsp-570.144.bin is 28M in size. Attached the diff I generated with some pre-subistitution for easier comparision. If you might not need firmware-nvidia-graphics, then removing it might be an option an regenerating the initramfs. Regards, Salvatore --- initrd.img-6.12.38+deb13-amd64.lsinitramfs 2025-09-06 14:21:01.802592225 +0200 +++ initrd.img-6.16.3+deb14-amd64.lsinitramfs 2025-09-06 14:21:22.578709716 +0200 @@ -20,27 +20,25 @@ usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/camellia-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/cast5-avx-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/cast6-avx-x86_64.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/chacha-x86_64.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/crc32-pclmul.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/crc32c-intel.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/crct10dif-pclmul.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/curve25519-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/des3_ede-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/ghash-clmulni-intel.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/nhpoly1305-avx2.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/nhpoly1305-sse2.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/poly1305-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/serpent-avx-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/serpent-avx2.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/serpent-sse2-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/sha1-ssse3.ko.xz -usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/sha256-ssse3.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/sha512-ssse3.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/twofish-avx-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/twofish-x86_64-3way.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/crypto/twofish-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/arch/x86/kvm usr/lib/modules/VERSION-amd64/kernel/arch/x86/kvm/kvm.ko.xz +usr/lib/modules/VERSION-amd64/kernel/arch/x86/lib +usr/lib/modules/VERSION-amd64/kernel/arch/x86/lib/crypto +usr/lib/modules/VERSION-amd64/kernel/arch/x86/lib/crypto/chacha-x86_64.ko.xz +usr/lib/modules/VERSION-amd64/kernel/arch/x86/lib/crypto/poly1305-x86_64.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto usr/lib/modules/VERSION-amd64/kernel/crypto/adiantum.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/aegis128.ko.xz @@ -69,15 +67,14 @@ usr/lib/modules/VERSION-amd64/kernel/crypto/cast6_generic.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/cast_common.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/ccm.ko.xz +usr/lib/modules/VERSION-amd64/kernel/crypto/chacha.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/chacha20poly1305.ko.xz -usr/lib/modules/VERSION-amd64/kernel/crypto/chacha_generic.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/cmac.ko.xz -usr/lib/modules/VERSION-amd64/kernel/crypto/crc32_generic.ko.xz -usr/lib/modules/VERSION-amd64/kernel/crypto/crc32c_generic.ko.xz +usr/lib/modules/VERSION-amd64/kernel/crypto/crc32-cryptoapi.ko.xz +usr/lib/modules/VERSION-amd64/kernel/crypto/crc32c-cryptoapi.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/cryptd.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/crypto_engine.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/crypto_null.ko.xz -usr/lib/modules/VERSION-amd64/kernel/crypto/crypto_simd.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/crypto_user.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/cts.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/curve25519-generic.ko.xz @@ -90,7 +87,9 @@ usr/lib/modules/VERSION-amd64/kernel/crypto/gcm.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/geniv.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/ghash-generic.ko.xz -usr/lib/modules/VERSION-amd64/kernel/crypto/keywrap.ko.xz +usr/lib/modules/VERSION-amd64/kernel/crypto/krb5 +usr/lib/modules/VERSION-amd64/kernel/crypto/krb5/krb5.ko.xz +usr/lib/modules/VERSION-amd64/kernel/crypto/krb5enc.ko.xz usr/lib/modules/VERSION-amd64/kernel/crypto/lrw.
Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Source: linux Version: 6.16.3-1 Severity: normal Hi, Not sure if this is actionable and indeed beyond expectations, but just in case this points at a problem in the packaging. Feel free to close if I just need to deal with this. I just upgraded my forky system and the upgrade failed: update-initramfs: Generating /boot/initrd.img-6.16.3+deb14-amd64 zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -9 -T0 70 update-initramfs: failed for /boot/initrd.img-6.16.3+deb14-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.16.3+deb14-amd64 (--configure): installed linux-image-6.16.3+deb14-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-libc-dev (6.16.3-1) ... dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.16.3+deb14-amd64 (= 6.16.3-1); however: Package linux-image-6.16.3+deb14-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.16.3+deb14-amd64 linux-image-amd64 Error: Sub-process /usr/bin/dpkg returned an error code (1) I don't have a big /boot system, as the default boot partition used to be (way too) small. I recall that I once enable something to only install required modules into the initrd, which helped me along until today. /boot right after upgrade: paul@toba ~ $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 456M 281M 151M 66% /boot paul@toba ~ $ ls -al /boot/ total 273416 drwxr-xr-x 5 root root 1024 Aug 30 17:32 . drwxr-xr-x 18 root root 4096 Aug 30 17:31 .. -rw-r--r-- 1 root root283225 Jul 3 21:01 config-6.12.35+deb13-amd64 -rw-r--r-- 1 root root283270 Jul 16 09:13 config-6.12.38+deb13-amd64 -rw-r--r-- 1 root root289665 Aug 24 23:29 config-6.16.3+deb14-amd64 drwx-- 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 1024 Aug 20 18:36 grub -rw-r--r-- 1 root root 120238850 Jul 22 19:33 initrd.img-6.12.35+deb13-amd64 -rw-r--r-- 1 root root 120394731 Aug 30 08:39 initrd.img-6.12.38+deb13-amd64 drwx-- 2 root root 12288 Nov 17 2024 lost+found -rw-r--r-- 1 root root83 Jul 3 21:01 System.map-6.12.35+deb13-amd64 -rw-r--r-- 1 root root83 Jul 16 09:13 System.map-6.12.38+deb13-amd64 -rw-r--r-- 1 root root92 Aug 24 23:29 System.map-6.16.3+deb14-amd64 -rw-r--r-- 1 root root 12093376 Jul 3 21:01 vmlinuz-6.12.35+deb13-amd64 -rw-r--r-- 1 root root 12097472 Jul 16 09:13 vmlinuz-6.12.38+deb13-amd64 -rw-r--r-- 1 root root 13162432 Aug 24 23:29 vmlinuz-6.16.3+deb14-amd64 /boot after $(sudo apt remove linux-image-6.12.35+deb13-amd64): paul@toba ~ $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 456M 337M 95M 79% /boot paul@toba ~ $ ls -al /boot/ total 330986 drwxr-xr-x 5 root root 1024 Aug 30 17:36 . drwxr-xr-x 18 root root 4096 Aug 30 17:35 .. -rw-r--r-- 1 root root283270 Jul 16 09:13 config-6.12.38+deb13-amd64 -rw-r--r-- 1 root root289665 Aug 24 23:29 config-6.16.3+deb14-amd64 drwx-- 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 1024 Aug 30 17:36 grub -rw-r--r-- 1 root root 120394731 Aug 30 08:39 initrd.img-6.12.38+deb13-amd64 -rw-r--r-- 1 root root 191341702 Aug 30 17:36 initrd.img-6.16.3+deb14-amd64 drwx-- 2 root root 12288 Nov 17 2024 lost+found -rw-r--r-- 1 root root83 Jul 16 09:13 System.map-6.12.38+deb13-amd64 -rw-r--r-- 1 root root92 Aug 24 23:29 System.map-6.16.3+deb14-amd64 -rw-r--r-- 1 root root 12097472 Jul 16 09:13 vmlinuz-6.12.38+deb13-amd64 -rw-r--r-- 1 root root 13162432 Aug 24 23:29 vmlinuz-6.16.3+deb14-amd64 Note the increase from 120394731 to 191341702 for the initrd. Paul -- System Information: Debian Release: forky/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.38+deb13-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature.asc Description: OpenPGP digital signature
