Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #89044 > unrolled thread

Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE

Started byPaul Gevers <elbrus@debian.org>
First post2025-08-30 18:00 +0200
Last post2025-09-06 11:50 +0200
Articles 7 — 4 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Paul Gevers <elbrus@debian.org> - 2025-08-30 18:00 +0200
    Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Salvatore Bonaccorso <carnil@debian.org> - 2025-09-06 11:50 +0200
      Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Paul Gevers <elbrus@debian.org> - 2025-09-06 14:10 +0200
        Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Salvatore Bonaccorso <carnil@debian.org> - 2025-09-06 14:40 +0200
          Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Ben Hutchings <ben@decadent.org.uk> - 2025-09-07 23:20 +0200
          Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE Paul Gevers <elbrus@debian.org> - 2025-09-27 13:40 +0200
    Processed: Re: Bug#1112541: linux: initrd grew significantly from  6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-09-06 11:50 +0200

#89044 — Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE

FromPaul Gevers <elbrus@debian.org>
Date2025-08-30 18:00 +0200
SubjectBug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Message-ID<Lpw9H-bwJH-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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 root    283225 Jul  3 21:01 config-6.12.35+deb13-amd64
-rw-r--r--  1 root root    283270 Jul 16 09:13 config-6.12.38+deb13-amd64
-rw-r--r--  1 root root    289665 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 root        83 Jul  3 21:01 
System.map-6.12.35+deb13-amd64
-rw-r--r--  1 root root        83 Jul 16 09:13 
System.map-6.12.38+deb13-amd64
-rw-r--r--  1 root root        92 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 root    283270 Jul 16 09:13 config-6.12.38+deb13-amd64
-rw-r--r--  1 root root    289665 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 root        83 Jul 16 09:13 
System.map-6.12.38+deb13-amd64
-rw-r--r--  1 root root        92 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

[toc] | [next] | [standalone]

#89086

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-09-06 11:50 +0200
Message-ID<LrXIt-ddG6-1@gated-at.bofh.it>
In reply to#89044
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 root    283225 Jul  3 21:01 config-6.12.35+deb13-amd64
> -rw-r--r--  1 root root    283270 Jul 16 09:13 config-6.12.38+deb13-amd64
> -rw-r--r--  1 root root    289665 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 root        83 Jul  3 21:01
> System.map-6.12.35+deb13-amd64
> -rw-r--r--  1 root root        83 Jul 16 09:13
> System.map-6.12.38+deb13-amd64
> -rw-r--r--  1 root root        92 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 root    283270 Jul 16 09:13 config-6.12.38+deb13-amd64
> -rw-r--r--  1 root root    289665 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 root        83 Jul 16 09:13
> System.map-6.12.38+deb13-amd64
> -rw-r--r--  1 root root        92 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

[toc] | [prev] | [next] | [standalone]

#89091

FromPaul Gevers <elbrus@debian.org>
Date2025-09-06 14:10 +0200
Message-ID<LrZTX-dfoR-13@gated-at.bofh.it>
In reply to#89086

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#89093

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-09-06 14:40 +0200
Message-ID<Ls0mZ-dfEE-1@gated-at.bofh.it>
In reply to#89091

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#89123

FromBen Hutchings <ben@decadent.org.uk>
Date2025-09-07 23:20 +0200
Message-ID<LsuXL-dBgL-11@gated-at.bofh.it>
In reply to#89093

[Multipart message — attachments visible in raw view] — view raw

On Sat, 6 Sep 2025 14:37:30 +0200 Salvatore Bonaccorso
<carnil@debian.org> 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.

[toc] | [prev] | [next] | [standalone]

#89423

FromPaul Gevers <elbrus@debian.org>
Date2025-09-27 13:40 +0200
Message-ID<LzBrr-XBg-5@gated-at.bofh.it>
In reply to#89093

[Multipart message — attachments visible in raw view] — view raw

Hi,

On Sat, 6 Sep 2025 14:37:30 +0200 Salvatore Bonaccorso 
<carnil@debian.org> 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

[toc] | [prev] | [next] | [standalone]

#89087 — Processed: Re: Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-09-06 11:50 +0200
SubjectProcessed: Re: Bug#1112541: linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Message-ID<LrXIt-ddG6-3@gated-at.bofh.it>
In reply to#89044
Processing control commands:

> tags -1 + moreinfo
Bug #1112541 [src:linux] linux: initrd grew significantly from 6.12.38+deb13 to 6.16.3+deb14 causing ENOSPACE
Added tag(s) moreinfo.

-- 
1112541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112541
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web