This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.
Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589
The terrible thing with compression is how we know of no universal rule.
I'm sure you can even find non-pathological cases where lz4 compresses
better than zpaq (and does so 100 times faster). And that's without
taking I/O into account (or filters).
An important thing to keep in mind here is
@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
Hi guys, I want to share my success story:
It happened after I've updated to CUDA repo's nvidia drivers :) my
`initrd.img-5.15.0-58-generic` (`ls -lah /boot`) was about 192M and using
tuning option of the `/etc/initramfs-tools/initramfs.conf` file I've decreased
it (`sudo update-initramfs -c -k
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally
Backporting to LTS is a good idea IMHO. A few additional use cases to
consider
- Users on the threshold who experience slight initrd image growth due
to any module update
- Users who thought they might be able to continue just using older
images may fail to recognize grub will eventually remove
I second backporting this to jammy at least as it is an LTS.
--
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
** Tags added: originate-from-2000298
--
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:
Hi, There are a few OEM platforms that also requires these memory
patches in grub2 on jammy, could we also port 2.06-2ubuntu16 back to
jammy?
** Tags added: originate-from-1998995
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package grub2-unsigned - 2.06-2ubuntu16
---
grub2-unsigned (2.06-2ubuntu16) lunar; urgency=medium
* Cherry-pick all memory patches from rhboot
- Allocate initrd > 4 GB (LP: #1842320)
- Allocate kernels as code, not data (needed for newer firmware)
Can confirm on 22.10, Lenovo Yoga 720 (4k display). Is there no fix for
this other than trying to mess with initramfs compression settings? Is
that expected to be the normal user case?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Description changed:
[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.
*
juliank, edited and removed more notes as you advised. I hope my edits
per your advice help clarify things and help anyone to see if a new bug
is necessary to report. Thanks for your input.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.
Not using the same language as everyone else and writing very long
comments makes it hard to understand.
First I thought you reported an out of memory
Hi juliank, I understand completely you want me to have insights related
to verification of the update in lunar-proposed and that I am confusing
you with my #131 post.
I was mentioning that to help people who need the triage, since it is
not possible to say locked out nor without updates until
Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.
--
You received this bug notification because you are a
Bringing one the original triage fixes I posted in #41 and #45 after
gathering some information on changes to grub2 for Raspberry Pi that
exposed this issue (i.e., I know the fix to get things to boot), after
upgrading to 22.10, I now have an updated set of events on a specific
kernel.
I still
** Changed in: grub2-unsigned (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: grub2-signed (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm insanely late on this, but I couldn't help but notice that nobody
mentioned Ventoy (at least ctrl+f doesn't return any results in the full
activity log for "ventoy")
Since installing via Rufus set to ISO mode has been a suggested work-
around, wouldn't this by definition mean that using
I have now picked all the rhboot patches in 2.06-2ubuntu16~ppa1 in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
and will boot that before uploading to the archive.
This *should* allow initrds over 4GB but obviously bugs could be there.
The important bit is that we are now
** Tags added: originate-from-1998320 somerville
--
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
Jeremy, there are duplicate firmware files. Replacing duplicates with
symlinks is probably the easiest and most efficient way to improve the
situation.
I get the following:
> % jdupes -mrS /lib/firmware
> Scanning: 2830 files, 286 items (in 1 specified)
> 405 duplicate files (in 212 sets),
** Description changed:
+ [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.
*
Ah, didn't realize Debian had a different limit. Thanks @juliank.
@anourzad, I'm not sure I would want to start adding custom steps to the
kernel update path. I'm much more inclined to add an /etc option for a
supported automatic mechanism, like compression or module selection.
@adrien-n, great
Is it possible if we have an overwrite in debian/rule by using something
like DEB_BUILD_ARCH to specify higher compression rate for amd64?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I put together some notes and work-arounds in order to provide a simpler
reference for people hitting this issue. I didn't test everything below
but nothing should be risky.
# Summary
Grub attempts to read the initrd into a memory location that is too
small.
This issue is caused by a
@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
can this be a solution ?
https://stackoverflow.com/questions/2895816/how-do-i-strip-local-
symbols-from-linux-kernel-module-without-breaking-it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Confirmed that reducing the size of the initrd.img slightly allowed my
machine to boot. I just enabled `COMPRESSLEVEL=19` with `COMPRESS=zstd`
(default on debian) in initramfs.conf. That reduced my initrd.img size
from 72MB to 62MB, which allowed my machine to boot.
Ultimately, I set
The issue happened for me after installing newer nvidia proprietary drivers
(515 and also 520).
The only way to recover was to boot using a previous installed kernel (I used
rescue mode. The rescue mode in current kernel still gives the same error)
Not sure how this helps this bug
** Changed in: grub2-unsigned (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: grub2-signed (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: fr-2934
--
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
-> If an user somehow met this issue, then the system is not able to
boot.
It can boot, if it did previously, and this issue will get fixed pretty
quick IMHO in the updates repository given it impacts current 20.04,
22.04 and 22.10.
Here is just the workaround part, for current 22.10 or 22.04 to
I don't think "MODULES=dep" is the proper workaround for this.
If an user somehow met this issue, then the system is not able to boot.
Users need to do many extra works to find out this workaround and do apply
unless we make "MODULES=dep" as default setting in initramfs configs (but I
don't
My XPS 13 9380 (no luks) also triggers this on 5.19 after the 22.10
upgrade; I can see the initrd is about 7% bigger in 22.10 over 22.04.
-rw-r--r-- 1 root root 111203941 Oct 30 18:16 initrd.img-5.15.0-52-generic
-rw-r--r-- 1 root root 120222346 Oct 31 21:39 initrd.img-5.19.0-23-generic
#103
Download ubuntu-20.04.5-desktop-amd64.iso and try to install on a HP
laptop, I can't boot into installation menu. If initrd.img lower than
100MB then everything is fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If possible, I still expect we can make grub supports to boot from
bigger initramfs.
There will still have users to meet this issue in the future if their
initramfs somehow bigger as long as we don't choose use higher
compression as workaround (for ubuntu desktop / server).
--
You received this
** Tags added: originate-from-1994098 stella
--
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
initramfs-tools 0.142 added support for specifying the compression
level. Ubuntu will probably merge this version for Ubuntu 23.04.
--
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
I upgraded from 22.04.1 to 22.10. Issue returned as
/usr/sbin/mkinitramfs was changed to default. Had to follow my previous
steps shown after #41 . . . zstd had defaulted to a lower compression
value in /usr/sbin/mkinitramfs at 1 instead of 19. I changed line 196 to
19 compression
zstd)
As I've said elsewhere, if we dedup firmware files through symlinks, we
can save 10MB in initrds. Compression does not help because the
compressors have very small compression windows and cannot see
redundancy in practice (this applies to xz to a lesser extent but even
for xz there is an
Really the workaround is to set MODULES=dep in /etc/initramfs-
tools/initramfs.conf, this yields a much smaller initramfs (but you
can't take out the disk and boot it in another machine), disabling
secure boot or sgx should not be doing anything.
** Also affects: grub2-unsigned (Ubuntu)
I can replicate this on my Dell XPS13 9380 (no encryption). Occurs as well with
Ubuntu 20.04 LTS, but not with 18.04 LTS, so not sure if it is related to the
same reason?
-> Disabling Secure Boot and SGX did not resolve the issue
--
You received this bug notification because you are a member
Duplicate bug 1970402 mentions that:
> Workaround: Disable Secure Boot and SGX.
works for multiple people.
--
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:
Another workaround might be to use Ubuntu's own compressed image with a
preinstalled Ubuntu Server (although not officially released) according
to the following link
https://ubuntuforums.org/showthread.php?t=2474692
Scroll down to read also the following posts, that describe how to
install
Workaround:
You can usually install Ubuntu on a drive in one machine and then move
the drive into another machine.
At least I think that's what I did on the affected machine with 22.04,
which is why I never discovered this bug until 22.10 development
started.
--
You received this bug
When is this going to be fixed and is there a work-around. I have tried
both updating from 20.04 and direct installation of 22.04 and have found
this problem preventing me from using 22.04 [it never boots]. I have two
computers. One is a Dell with nvidia drivers [the perfect target machine
to
OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed => Triaged
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Our goal should be to merge the entire patch series into kinetic, worst
case, kinetic will not be installable for some users. This means we will
have decent results from people trying that in the next 4 weeks (by Oct
27 the release has been out 1 week).
In the meantime, next week we should push
I don't have such "there is allways that machine (or bad firmware) that nobody
heard of that will fail" case from my hand but it's frustrated if it becomes a
blocker for fixing the bug for new devices from market.
However, I understand how users feel helpless if a SRU introduces a regression
I've been asked to prepare a summary of the current status of this bug:
- there's a grub2 security update that's been published and then pulled:
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu10/+publishinghistory
Hi Julian,
I didn't see the 'boot failures on older system' from comment#90.
Would you please point it out more specifically?
--
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
@jeremyszu (os369510) Did you see #90, it seems your patch would cause
boot failures on older system unable to handle this memory range.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I tested latest daily build
https://cdimage.ubuntu.com/jammy/daily-live/20220920/jammy-desktop-amd64.iso
and out of memory stil exist. I hope someone can provide an iso for download
with a livesystem and install for jammy with changed compression.
Ubuntu 21.10 (out of support) and Fedora 36
Unfortunately the steps in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/89
aren't working for me (I'm a professional developer, am confident i've
followed the steps properly, have tried three times)
Does anyone else have any other workarounds?
--
You received this bug
Add one more case caused by this issue:
When SEV is enabled on the host, the guest also enables SEV and running 5.15
kernel
with this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12
The SWIOTLB driver in the guest
** Tags added: foundations-todo
--
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:
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie"
Hi Mauricio,
From the patch set in this ticket:
```
+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
+0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
Earlier today, I upgraded my Mint 20.3 system to Mint 21.0 and got this
"out of memory" issue (Asus ROG G752VT laptop.).
The fix in comment #41 and #89 worked (changing the compression to 19),
but a lot of the steps were not needed.
This is the minimal steps needed, (maybe fewer possible,
I found if the Max TOLUD is set to 1GB or higher in the BIOS (anything
other than dynamic) then Ubuntu 22.04 ISO will not get this out of
memory error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi renton,
If you want to build it by yourself, then you should clone this:
https://people.canonical.com/~jeremysu/lp1842320/
and built it locally and don't clear the build environment, you can
found the efi binary on "obj/monolithic/grub-efi-amd64/grubx64.efi". I
personally use pbuilder with
I am getting this error and cannot even boot Ubuntu 22.04.1 from a live
USB. I am using an HP Elite Dragonfly G2 with 16GB of RAM. I get an
error: out of memory message then a kernel panic. Please fix this, I
would very much like to try running Ubuntu but I have to run Fedora 36
instead due to the
Hi, @jeremyszu
How can I build grub from your repository
https://github.com/os369510/grub2 with your patches for testing my linux
box?
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this
A couple of days ago I upgraded my 21.10 system to 22.04 and got this
"out of memory" issue (Dell XPS 15 9550 with 3840x2160 display).
The fix in comment #41 worked (changing the compression to 19), and the
sequence of commands in #44 helped. However, just noting that there are
several typos in
Confirmed affecting GIGABYTE Z690 AORUS ELITE DDR4 (LGA1700, USB 3.2,
PCIe 5.0) after installing nvidia-driver-515
--
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
Confirmed affecting Samsung Galaxy Book2 (i7-1255U, Intel Iris Xe
Graphics, 16GB LPDDR4x / NP750XED-KC4SE).
--
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:
This is also affecting the MSI MEG Z690I Unify motherboard; can not boot
any live disk images of Ubuntu 22.04
--
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:
Ben, XPS 13 should have no problems with the factory-installed certified (by
us) images:
https://ubuntu.com/certified?q=XPS+13=20=22.04+LTS
Certainly when we were certifying the latest XPS 13 Plus (with 4K), the
only blocking issue I saw was a multi-monitor bug that we fixed before
launch.
--
Joseph, out of interest, what model of XPS 13 do you have? I'm getting
new XPS 13 soon and wondering if it'll have the same issue (I guess it's
likely given the 4k screen).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@juliank: I was affected by this bug when upgrading to 22.04.1 from
20.04 at the weekend. (originally installed as 18.04)
Unfortunately the system did *not* auto-recover.
Manually picking the previous kernel options from grub gave the same
"error: out of memory."
I was able to recover the
This patch is not from upstream or rhboot but which has been submitted as a MP
to rhboot
https://github.com/rhboot/grub2/pull/102
+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
** Patch added:
"0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607435/+files/0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch
--
You received this bug notification because you are a
** Patch added:
"0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607434/+files/0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch
--
You received this bug notification because you are a
** Patch added: "0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607432/+files/0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
--
You received this bug notification because you are a member of
** Patch added: "0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607433/+files/0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch
--
You received this bug notification because you are a member of
** Patch added:
"0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607431/+files/0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
--
You received this bug notification because you are a
As my MP from comment#69 doesn't have response from rhboot team.
Shared the debdiff here for review to consider to carry it in Ubuntu.
** Patch added: "0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch"
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
You received
In case it's relevant...
I bricked my old PC while trying to work around this bug(!). After
putting the same RAM and plugging the same monitor into a new machine,
the bug does not occur. So the trigger for the bug was more to do with
the old machine's firmware.
--
You received this bug
As with comment #41, #44, and #45, has the decision been made to fix
grub2's memory issues or just the compression level change that was with
initramfs (as I believe it was a choice made to increase Raspberry Pie
boot times)?
--
You received this bug notification because you are a member of
83 matches
Mail list logo
