Test Day:2026-02-09 GRUB out of memory fix verification part 2

GRUB out of memory fix verification, part 2
Date	2026-02-09 to 2025-02-15
Time	all day
Website	QA/Test Days
Matrix	#test-day:fedoraproject.org(other clients|?)
Mailing list	test

Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

This Test Day will focus on testing a fix for an out of memory error (bz#2263643) that occurs on certain hardware when trying to install fedora. There is not enough memory to allocate the large installation initramfs, and as a result the installation cannot proceed. This is indeed a continuation of the first test day which unfortunately the test coverage did not catch some issues.

Note: This doesn't depend on the amount of RAM you have installed - you can have 64GB RAM and still be affected by this bug - nor the secondary disk space nor the file system type, this is particularly impacting some motherboards, e.g. ASUS.

There is a fix for this error, and we would like to have it tested on various hardware, both old and new. Any machine that you test with is welcome. The more results we have, the more certain we can be about the fix.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

• Development - Leo Sandoval (@lsandova:matrix.org), Marta Lewandowska (@marta-lewandowska:matrix.org)
• Quality - Lukáš Růžička (lruzicka), Adam Williamson (adamw), Petr Sklenář (psklenar), Jaroslav Groman (jgroman)

You can chat with us on Matrix. See the infobox on top of the page to learn where to join.

Prerequisite for Test Day

• A bare metal machine (no VM)
• Download the test live image and write it to a USB through Fedora Media Writer or dd.

How to test?

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ➕ (plus) button for that test case.

In the Profile field, please provide a short system description, e.g. hostnamectl | grep Hardware.

In the Comment field, if testing was successful: On your running system, install the lshw package (sudo dnf install lshw) and run hostnamectl ; lsblk -f; sudo lshw -short commands in a terminal. Copy the output and paste it into pastebin (set paste expiration to never), then take the URL of the paste and put it into the Comment field. In case testing was unsuccessful, provide any boot log or details observed during boot the same way as in the successful case, create a pastebin (set paste expiration to never), take the URL and paste it into the Comment field.

Test cases

ISO install

• Temporally Disable Secure boot
• Boot from the prepared USB drive (see Prerequisite for Test Day section above).
• If Live Fedora does not start:
  • Submit your results (see How to test? section above), you are done!
• If Live Fedora starts:
  • Install Fedora. The reason we are asking for full installation is that previous test day we did not ask testers this step and we ended up with bz#2427945.
  • Reboot your new Fedora System
  • Submit your results (see How to test? section above), you are done!

RPM install

Note: In case you have a running Fedora rawhide machine, please follow the below steps.

• Temporally disable Secure boot
• Boot your system
• Install the koji package, e.g. sudo dnf install koji
• Download the rpms koji taskID=141497105, e.g. koji download-task --arch=x86_64 --arch=noarch 142127319
• Install the rpms, e.g.sudo dnf install *.rpm
• Reboot
• If Fedora starts:
  • Submit your results (see How to test? section above), you are done!
• If Fedora does not start:
  • If you see error: ../../grub-core/kern/mm.c:552:out of memory. or any similar memory issue, please add a comment to bz#2263643.
  • If you see a different error or have some other problem, please file a new bug at https://bugzilla.redhat.com against grub2 component.
  • Submit your results (see How to test? section above), you are done!

Reporting bugs

All new bugs should be reported into Red Hat Bugzilla, in most cases against the grub2 component.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

• exact steps you've performed (and whether you can reproduce it again)
• screenshots or videos, if applicable
• (this does not really apply to grub) system journal (log), which you can retrieve by journalctl -b > journal.txt
• your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Exported results

User	Short system description, e.g. a desktop motherboard name, or laptop manufacturer + model name	Fresh boot	References
Jacob Scharmberg	LENOVO_MT_81C3_BU_idea_FM_YOGA 720-13IKB	pass
Jacob Scharmberg	Gigabyte B550M AORUS ELITE	pass
Jacob Scharmberg	HP Elite x2 1012 G2	pass
Jaroslav Groman	Gigabyte J3455N-D3H	pass
Michael Tadault	Asus ProArt Z790-CREATOR WIFI	pass
Michael Tadault	Gigabyte Z390 GAMING X	pass
Nie Lili	ThinkPad T490s	pass
Petr Sklenar	LENOVO_MT_21KW_BU_Think_FM_ThinkPad P1 Gen 7	pass