GNU GRUB - Bugs: bug #63607, Grub 2.06 enters rescue mode with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63607: Grub 2.06 enters rescue mode with "--enable-mm-debug" option on HP 350 G1 hardware
Submitter: | flooklab <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: | |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
(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.
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:
The original 2.06 release (commit ae94b97be2b81b625d6af6654d3ed79078b50ff6, package 2:2.06-5) works as expected.
Grub is installed with:
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:
System info: