@madzohan from my comment around #41 above and related workarounds from there downward, it seems you tried a different compression scheme and found a smaller size in this case from zstd to xz.
I looked over your settings and options for xz compression, but also reading the man pages for XZ it shows that it is already at a -6 setting by default that makes the dictionary size 8M and uses lzma2 compression. XZ settings are already at default in /etc/sbin/mkinitramfs . With your options it was a few MB larger than from xz default in my setup. I tried both xz settings. Finally, I switched back to zstd and my compression changes I made in /etc/sbin/mkinitramfs as my workaround. I got a good compression size, but people note online that zstd has great read speeds over xz no matter the compression level. So I decided to stay at zstd with only a 7 MB difference: from 125 MB on default xz to 131 MB on zstd with -q 22 compression in /etc/sbin/mkinitramfs . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x000000007dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x000000007dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x000000007dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x000000007bcd5a30 in ?? () #5 0x000000007fe21247 in ?? () #6 0x000000007bc030c8 in ?? () #7 0x000000017fe21238 in ?? () #8 0x000000007bcd5320 in ?? () #9 0x000000007fe21250 in ?? () #10 0x0000000000000000 in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type Start End # Pages Attributes Available 0000000000000000-0000000000086FFF 0000000000000087 000000000000000F BS_Data 0000000000087000-0000000000087FFF 0000000000000001 000000000000000F Available 0000000000088000-000000000009EFFF 0000000000000017 000000000000000F Reserved 000000000009F000-000000000009FFFF 0000000000000001 000000000000000F Available 0000000000100000-0000000000FFFFFF 0000000000000F00 000000000000000F LoaderCode 0000000001000000-0000000001021FFF 0000000000000022 000000000000000F Available 0000000001022000-00000000238A7FFF 0000000000022886 000000000000000F BS_Data 00000000238A8000-0000000023927FFF 0000000000000080 000000000000000F Available 0000000023928000-0000000028860FFF 0000000000004F39 000000000000000F BS_Data 0000000028861000-000000002AB09FFF 00000000000022A9 000000000000000F LoaderCode 000000002AB0A000-000000002ACF8FFF 00000000000001EF 000000000000000F BS_Data 000000002ACF9000-000000002B2FAFFF 0000000000000602 000000000000000F Available 000000002B2FB000-000000002B611FFF 0000000000000317 000000000000000F BS_Data 000000002B612000-000000002B630FFF 000000000000001F 000000000000000F Available 000000002B631000-000000002B632FFF 0000000000000002 000000000000000F BS_Data 000000002B633000-000000002B63CFFF 000000000000000A 000000000000000F Available 000000002B63D000-000000002B649FFF 000000000000000D 000000000000000F BS_Data 000000002B64A000-000000002B64EFFF 0000000000000005 000000000000000F Available 000000002B64F000-000000002B666FFF 0000000000000018 000000000000000F BS_Data 000000002B667000-000000002D8D5FFF 000000000000226F 000000000000000F LoaderCode 000000002D8D6000-000000002D8E9FFF 0000000000000014 000000000000000F BS_Data 000000002D8EA000-000000002D925FFF 000000000000003C 000000000000000F LoaderCode 000000002D926000-000000002D932FFF 000000000000000D 000000000000000F BS_Data 000000002D933000-000000002D969FFF 0000000000000037 000000000000000F BS_Code 000000002D96A000-000000002D973FFF 000000000000000A 000000000000000F BS_Data 000000002D974000-000000002E377FFF 0000000000000A04 000000000000000F Available 000000002E378000-000000002E37AFFF 0000000000000003 000000000000000F ... Reserved 000000003C08B000-000000004192FFFF 00000000000058A5 000000000000000F ACPI_NVS 0000000041930000-0000000041B2FFFF 0000000000000200 000000000000000F ACPI_Recl 0000000041B30000-0000000041BFEFFF 00000000000000CF 000000000000000F BS_Data 0000000041BFF000-0000000041BFFFFF 0000000000000001 000000000000000F Available 0000000100000000-00000002AB7FFFFF 00000000001AB800 000000000000000F Reserved 00000000000A0000-00000000000FFFFF 0000000000000060 0000000000000000 Reserved 0000000041C00000-0000000043FFFFFF 0000000000002400 0000000000000000 Reserved 0000000044000000-0000000047FFFFFF 0000000000004000 000000000000000F Reserved 0000000049400000-00000000495FFFFF 0000000000000200 000000000000000F Reserved 000000004C000000-000000004FFFFFFF 0000000000004000 0000000000000009 Reserved 0000000050000000-00000000547FFFFF 0000000000004800 0000000000000000 MMIO 00000000C0000000-00000000CFFFFFFF 0000000000010000 8000000000000001 Reserved 00000000FED20000-00000000FED7FFFF 0000000000000060 0000000000000000 MMIO 00000000FF800000-00000000FFFFFFFF 0000000000000800 8000000000001000 ... LoaderCode: 562 Pages (2,301,952 Bytes) LoaderData: 0 Pages (0 Bytes) ... Available : 1,917,598 Pages (7,854,481,408 Bytes) Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After cloning grub2 (2.06-2ubuntu16) from lunar-proposed and built, the results as following: 421M /boot/initrd.img-5.17.0-1021-oem # pass 453M /boot/initrd.img-5.17.0-1024-oem # pass 471M /boot/initrd.img-5.17.0-1024-oem # fail Only 453M is because verifier will consume the same memory size of initrd in <1G memories. The loadable initrd will locate at >4G if machine/kernel support it. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but it use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There are some “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system. If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * The package grub2 (2.06-2ubuntu16) is now in lunar-proposed. --- Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): total used free shared buff/cache available Mem: 7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic 5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System /dev/nvme0n1p2 1050624 2549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VG Fmt Attr PSize PFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g 0 $ sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao---- 474.75g swap_1 ubuntu-vg -wi-ao---- 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F.... pulseaudio CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1842320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
