[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #63607] Grub 2.06 enters rescue mode with "--enable-mm-debug" optio

From: flooklab
Subject: [bug #63607] Grub 2.06 enters rescue mode with "--enable-mm-debug" option on HP 350 G1 hardware
Date: Mon, 2 Jan 2023 12:50:49 -0500 (EST)


                 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
         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:

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
(GRUB commit 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
package 2:2.06-5
works as expected.

Grub is installed with:

# grub-install --target=x86_64-efi --efi-directory=/boot/efi
# 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:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]