URL: <https://savannah.gnu.org/bugs/?68226>
Summary: Problem with 64 bit bitmasks badram starting with
"f"
Group: GNU GRUB
Submitter: masc
Submitted: Fr 10 Apr 2026 09:15:47 UTC
Category: Booting
Severity: Major
Priority: 5 - Normal
Item Group: Software Error
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Unlocked
Release: other
Release:
Reproducibility: Every Time
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fr 10 Apr 2026 09:15:47 UTC By: M <masc>
One of my personal machines, non-ECC, started to have a broken memory area,
which I hoped to be able to mask easily using the GRUB_BADRAM setting.
However, GRUB failed to boot after setting something like
badram 0x000000008c4e0800,0xffffffffffffcfe0
Just black screen, thats it. Had to roll it back on the fs manually.
I found this article
https://unix.stackexchange.com/questions/746164/grub-hangs-itself-with-64bit-memtest86-badram-pattern
which also contains the quick-fix.
badram 0x000000008c4e0800,0x7fffffffffffcfe0
And because of the unlikely situation that someone would have to mask that
much RAM, that will likely never be a problem and thats likely also the reason
it may have never made it into a bug report. For completeness' sake I wanted
to make one anyway. Feel free to just abandon it.
This was tested with
GRUB 2.14~git20250718.0e36779-1ubuntu4 on Ubuntu 25.10
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68226>
_______________________________________________
Nachricht gesendet über Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
