This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2223883 - Error when loading large initrd (~1 GiB) on UEFI: out of memory
Summary: Error when loading large initrd (~1 GiB) on UEFI: out of memory
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: grub2
Version: 9.2
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-19 07:46 UTC by Juan Hernández
Modified: 2023-09-16 20:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-16 20:07:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4401 0 None Migrated None 2023-09-16 20:07:02 UTC
Red Hat Issue Tracker RHELPLAN-162685 0 None None None 2023-07-19 07:49:27 UTC

Description Juan Hernández 2023-07-19 07:46:35 UTC
Description of problem:

When we try to load a large initrd (~1 GiB) on UEFI with TPM disabled grub fails to load and prints a "out of memory" message.

Version-Release number of selected component (if applicable):

grub2-common-2.06-61.el9.noarch

How reproducible:

It always reproduces in the bare metal machine that we are using

  Model: Dell PowerEdge R340
  BIOS Version: 2.3.5
  iDRAC Firmware Version: 4.22.00.53

Steps to Reproduce:

1. Prepare a boot entry like this:

  set timeout=10
  set default=0
  menuentry 'Agent-Based Installer' {
    search --set=root --label agentboot
    load_video
    set gfx_payload=keep
    insmod gzio
    linux /images/pxeboot/vmlinuz random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.firstboot ignition.platform.id=metal ro
    initrd /images/pxeboot/initrd.img /images/ignition.img /images/pxeboot/rootfs.img
  }

What is most relevant of this boot entry is the size of the initrd files, specially the rootfs:

  # ls -lh pxeboot/initrd.img ignition.img pxeboot/rootfs.img 
  -r--r--r--. 1 root root 256K May  2 20:15 ignition.img
  -r--r--r--. 1 root root  81M May  2 20:20 pxeboot/initrd.img
  -r--r--r--. 1 root root 952M May  2 20:20 pxeboot/rootfs.img

Total size is approximately 1 GiB.

2. Ensure that TPM is enabled in the BIOS.

3. Boot the machine.

Actual results:

Grub fails with the following error message:

  error: ../../grub-core/kern/mm.c:552:out of memory.
  Press any key to continue...

After that the kernel is started anyhow, but it fails to locate the root filesystem and panics.

Expected results:

The initrd should be loaded and the machine should boot correctly.

Additional info:

We found that the issue is related to having TPM enabled. We applied the following patch to grub2-common-2.06-61.el9.noarch:

  https://github.com/rhboot/grub2/commit/b09440df05755c665cac9b93dd654e661c655c38

Then we rebuilt the RPM used the resulting grubx64.efi. With that the boot still fails in the same way. But it does work if we also disable TPM.

So the workaround is to disable TPM *and* apply the patch.

We would like to be able to boot with TPM enabled or disabled.

Comment 1 Marta Lewandowska 2023-08-08 12:34:47 UTC
Thanks for the patch, and thank you for your patience. :)

Comment 2 RHEL Program Management 2023-09-16 19:43:47 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-16 20:07:08 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.