URL: <https://savannah.gnu.org/bugs/?63607>
Summary: Grub 2.06 enters rescue mode with "--enable-mm-debug" option on HP 350 G1 hardware Project: GNU GRUB Submitter: trmailbin Submitted: Mon 02 Jan 2023 05:50:47 PM UTC Category: Booting Severity: Major Priority: 5 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Originator Name: Originator Email: Open/Closed: Open Release: Git master Release: Discussion Lock: Any Reproducibility: Every Time Planned Release: None _______________________________________________________ Follow-up Comments: ------------------------------------------------------- Date: Mon 02 Jan 2023 05:50:47 PM UTC By: flooklab <trmailbin> (Downstream bug report can be found here: https://bugs.archlinux.org/task/76062) I run an ArchLinux system with unmodified GRUB package from their official repository <https://archlinux.org/packages/core/x86_64/grub/>. Since package version 2:2.06.r261.g2f4430cc0-1 <https://github.com/archlinux/svntogit-packages/commit/ca6954b79e3a4058c749a3d5fbcad07d1967d93d> (GRUB commit 2f4430cc0a44fd8c8aa7aee5c51887667ad3d6c3 <https://git.savannah.gnu.org/cgit/grub.git/commit/?id=2f4430cc0a44fd8c8aa7aee5c51887667ad3d6c3>) I noticed that I cannot boot with freshly installed GRUB anymore, because it enters rescue mode right after the encrypted /boot key slot gets unlocked: error: symbol `grub_debug_malloc' not found. Unknown command `normal'. error: symbol `grub_debug_malloc' not found. Entering rescue mode... grub rescue> _ The original 2.06 release (commit ae94b97be2b81b625d6af6654d3ed79078b50ff6 <https://git.savannah.gnu.org/cgit/grub.git/commit/?id=ae94b97be2b81b625d6af6654d3ed79078b50ff6>, package 2:2.06-5 <https://github.com/archlinux/svntogit-packages/commit/a7fde4c59995b4c3355e6827871f7bd1f55025d6>) works as expected. Grub is installed with: # grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ArchLinux # grub-mkconfig -o /boot/grub/grub.cfg For some reason the ArchLinux package is compiled with the '--enable-mm-debug' option. *If I compile any version _without_ that option I can successfully boot again.* Is this maybe just a downstream issue from them using the '--enable-mm-debug' option, or should this not happen at all? Steps to reproduce: 1. install grub > 2.06 2. Generate grub config 3. Reboot 4. Unlock /boot slot System info: * Linux Distribution: ArchLinux * Hardware: HP 350 G1 laptop * Grub version: Git master > 2.06 tag * Booting in UEFI mode & using cryptodisk feature with LUKS-encrypted /boot _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63607> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/