[Solved-Updated] GRUB 'Out of Memory' bug fix issued, but...

[elaterite]

The GRUB2 bug (LP: #1842320) causing the "Out of Memory" at boot has been fixed and an update was issued for both kinetic and jammy.

So I went over to LaunchPad and downloaded the file: grub2-signed_1.187.3~22.04.1.tar.xz for jammy 22.04.1 (base for Linux Mint 21.1).

But there's no ./configure, readme, or install instructions, just a makefile.

How do I install this update?

Thanks!

[mbott001]

I thought I'd have to wait on the fix to come through the Package Manager.

--
Mike

[SMG]

The GRUB2 bug (LP: #1842320) causing the "Out of Memory" at boot has been fixed and an update was issued for both kinetic and jammy.

So I went over to LaunchPad and downloaded the file: grub2-signed_1.187.3~22.04.1.tar.xz for jammy 22.04.1 (base for Linux Mint 21.1).

But there's no ./configure, readme, or install instructions, just a makefile.

How do I install this update?

The usual process is to wait for the updates to come through the normal channels and install it like any other package update.

Is there a specific reason you thought you would need to do something different for this package update?

[elaterite]

Hi all -

My apologies. I didn't receive an email notification that people had responded.

So ya, I would like to get the patch installed because my machine won't boot with the latest kernels or NVIDIA drivers.

I had to edit GRUB to only boot 5.15.0-58-generic, and that still pauses for a long while at boot on the "out of memory" bug, but finally gets past it.

About a week ago I noticed in apt that grub-efi-amd64-bin & grub-efi-amd64-signed were being held back.

A couple of days ago shim-signed & ubuntu-advantage-tools showed up as being held back as well. Looks like maybe developers are addressing dependency issues?

I've read the fix will be in 21.2. But that won't be released until June.

Not that it's a big deal for me, I've got my machine working with bailing wire, mostly I'm concerned that anyone new to Linux Mint find it clunky and move on back to macOS or Windows.

I guess I could force apt to install the held back packages, but I'm guessing that would just break things (or something).

Thoughts?

[SMG]

So ya, I would like to get the patch installed because my machine won't boot with the latest kernels or NVIDIA drivers.

Others with Nvidia drivers have been able to boot with the latest kernels. There are multiple workarounds with which people have had success including this post and the other options listed here.

I've read the fix will be in 21.2. But that won't be released until June.

I do not know what you read.

About a week ago I noticed in apt that grub-efi-amd64-bin & grub-efi-amd64-signed were being held back.

A couple of days ago shim-signed & ubuntu-advantage-tools showed up as being held back as well. Looks like maybe developers are addressing dependency issues?

We presume that is what is happening. Others have be trying to force the installation anyhow, but that is not working (and really should not be done anyhow).

Not that it's a big deal for me, I've got my machine working with bailing wire, mostly I'm concerned that anyone new to Linux Mint find it clunky and move on back to macOS or Windows.

The issue is listed in the Linux Mint release notes for all LM21 versions. People have been posting on the forum since LM21 was released and getting their issue resolved so I can not speak to your concern.

[elaterite]

Yup, thanks, I've read the release notes and tried all of the work around hacks. Like I said, machine barely boots but only with much older kernel and NVIDIA drivers. Simply would like to update as I do graphics work. Although, admittedly, I have no clue if anything would be gained by updating. Just worried, given the machine hangs on the bug for a long time before finally booting that one little change could make my machine a no-boot.

Saw the GRUB fix being committed to Ubuntu 22.04.2 (Mint 21.2) at the top of the LP: #1842320 page under "milestone".

Thanks for the help. Guess I'll just have to wait until June for LM 21.2.

[SMG]

Saw the GRUB fix being committed to Ubuntu 22.04.2 (Mint 21.2) at the top of the LP: #1842320 page under "milestone".

Thanks for the help. Guess I'll just have to wait until June for LM 21.2.

I have no idea why you think Mint21.2 equates to Ubuntu 22.04.2. All versions of Mint 21 are based on Ubuntu 22.04 and receive jammy updates as they come through. I expect that grub fix to come to Linux Mint users long before June.

The Linux Mint ISOs have all the updates available to jammy at the time the ISO is made. They are not based on Ubuntu point releases.

[elaterite]

I hope it comes through sooner rather than later. So LM doesn't follow, with some delay, Ubuntu's point release cycle? It looks like it to me, but then I'm no developer.

[SMG]

I hope it comes through sooner rather than later.

Did you check to see if it came through yet? The bug link you listed is for OEM and not regular jammy, but looking through it, it says,
"This bug was fixed in the package grub2-unsigned - 2.06-2ubuntu14.1" and
"This bug was fixed in the package grub2-signed - 1.187.3~22.04.1"

I don't know if those packages are different for OEM versus regular.

So LM doesn't follow, with some delay, Ubuntu's point release cycle?

No.

[elaterite]

Here's what apt reports:

Code: Select all

bob@elaterite1:~$ sudo apt-get upgrade
[sudo] password for bob:       
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
----snip!----
The following packages have been kept back:
  grub-efi-amd64-bin grub-efi-amd64-signed
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
bob@elaterite1:~$ 

So I'm guessing there's unmet dependencies, eh? I think earlier you said (or someone said) people have tried to force the upgrade but it breaks stuff.

[SMG]

So I'm guessing there's unmet dependencies, eh? I think earlier you said (or someone said) people have tried to force the upgrade but it breaks stuff.

When one has unmet dependencies, there is a message which literally says "The following packages have unmet dependencies:" and then it lists the dependencies which have not been met.

I don't know what you snipped, but others have posted they are now getting a message if the packages being held back are part of a phased update. Phased updates are being done so if there are problems they stop the update and fix it before it goes to everyone.

[elaterite]

Okay, thanks for the info. I'll wait.

The "snip!" part was just an old kernel that could be removed with autoremove.

I'll mark this "solved."

[SMG]

This post has the "Phased updates" message I referenced. Maybe it's on a timed schedule as to when it would show? I don't know.

[elaterite]

Update:

Yesterday a linux-firmware update came through and I installed it.

This morning my machine failed to boot.

I managed to get it to boot using an yet older kernel than what my hack workaround has been. It booted, but the graphics were a mess, very low resolution. So backed up my home directories, and figuring the machine installation was borked, prepared to go back to LM 20.3.

But, I thought, since the 21.1 installation is toast, I'd go ahead and first try forcing the install of the Grub bug fix that was being held back in apt using the following code:

Code: Select all

sudo apt-get --with-new-pkgs upgrade grub-efi-amd64-bin grub-efi-amd64-signed

After that, I edited my Grub configuration hack to boot the latest kernel and updated Grub. Then I installed the latest NVIDIA drivers.

That fixed everything. Now I'm running the latest kernel AND the latest NVIDIA drivers. Machine boots and runs fine.

I'll mark this thread as [Solved-Updated].

[SMG]

Update:

Yesterday a linux-firmware update came through and I installed it.

This is the Changelog linux-firmware for jammy

Code: Select all

linux-firmware (20220329.git681281e4-0ubuntu3.11) jammy; urgency=medium

  * Add firmware for amdgpu products with GC 11.01 (LP: #2008113)
    - amdgpu: Add DCN 3.1.4 firmware
    - amdgpu: Add GC 11.0.1 firmware
    - amdgpu: Add SDMA 6.0.1 fimware
    - amdgpu: Add PSP 13.0.4 firmware
    - amdgpu: Add VCN 4.0.2 firmware
    - amdgpu: Update GC 11.0.1 firmware
  * Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 (LP: #2006458)
    - WHENCE: ath11k: move regdb.bin before board-2.bin
    - ath11k: WCN6855 hw2.0: update board-2.bin
    - ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
  * Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi frequently (LP: #2007875)
    - iwlwifi: add new FWs from core70-87 release
  * mt7921: add support of MTFG table (LP: #2009642)
    - linux-firmware: update firmware for MT7922 WiFi device

No clue why that would affect your computer's ability to boot, but then again you have not posted any information about your computer's hardware.

[elaterite]

No clue why that would affect your computer's ability to boot, but then again you have not posted any information about your computer's hardware.

I've no clue either. But I'd be curious if you can find something. So here you go! (Note: Machine booted, barely, before the linux-firmware update. It still hung on the "out of memory" message but after ten seconds or so it would continue to boot. After the update last night, when I powered on in the morning it halted with a kernel panic. In some of the messages before it stopped I did see some references to initramfs. Which is what the Grub out of memory bug is about.)

Code: Select all

~$ inxi -Fxz 
System:
  Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: MSI model: X99A SLI PLUS(MS-7885) v: 1.0
    serial: <superuser required> UEFI: American Megatrends v: 1.E0
    date: 06/15/2018
CPU:
  Info: 6-core model: Intel Core i7-5820K bits: 64 type: MT MCP arch: Haswell
    rev: 2 cache: L1: 384 KiB L2: 1.5 MiB L3: 15 MiB
  Speed (MHz): avg: 1256 high: 1624 min/max: 1200/3600 cores: 1: 1200
    2: 1298 3: 1202 4: 1200 5: 1201 6: 1624 7: 1200 8: 1200 9: 1202 10: 1289
    11: 1202 12: 1262 bogomips: 79204
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia
    v: 525.85.05 bus-ID: 04:00.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 2560x1440~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 950/PCIe/SSE2
    v: 4.6.0 NVIDIA 525.85.05 direct render: Yes
Audio:
  Device-1: Intel C610/X99 series HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Device-2: NVIDIA GM206 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel bus-ID: 04:00.1
  Sound Server-1: ALSA v: k5.15.0-67-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Ethernet I218-V vendor: Micro-Star MSI driver: e1000e
    v: kernel port: f020 bus-ID: 00:19.0
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Lite-On driver: ath10k_pci v: kernel bus-ID: 03:00.0
  IF: wls4 state: up mac: <filter>
Drives:
  Local Storage: total: 3.87 TiB used: 880.74 GiB (22.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 250GB
    size: 232.89 GiB temp: 40.9 C
  ID-2: /dev/sda vendor: Western Digital model: WD1003FZEX-00MK2A0
    size: 931.51 GiB
  ID-3: /dev/sdb vendor: Western Digital model: WD1003FZEX-00K3CA0
    size: 931.51 GiB
  ID-4: /dev/sdc vendor: Western Digital model: WD2003FZEX-00SRLA0
    size: 1.82 TiB
Partition:
  ID-1: / size: 213 GiB used: 18.92 GiB (8.9%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 524 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 14.9 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 26.0 C mobo: N/A gpu: nvidia temp: 40 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 322 Uptime: 1h 4m Memory: 31.25 GiB used: 4.01 GiB (12.8%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2600 Shell: Bash
  v: 5.1.16 inxi: 3.3.13

[SMG]

It booted, but the graphics were a mess, very low resolution.

This type of situation can be an indication the nouveau display driver loaded faster than nvidia and thus nvidia never loaded. That is a common situation and the workaround in [SOLVED] this post addresses it.

Your wireless driver is not exactly the same as the one in the linux-firmware update (ath11k), but it is similar. The explanation for the bug fix mentions ACPI settings, but I don't know if that might be relevant to your situation. I have seen where a bad network device (wifi or ethernet) can prevent a computer from booting/cause graphics issues.

Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: Lite-On driver: ath10k_pci v: kernel bus-ID: 03:00.0
IF: wls4 state: up mac: <filter>

However, the fact you installed the other packages (grub-efi) and all was well seems to indicate to me the update was not related to the problem you had. It may be a coincidence you had the issue after the update and the issue might have randomly happened even if you did not do the update. That is my guess at this point.