[bug #68226] Problem with 64 bit bitmasks badram starting with "f"

M <[email protected]> Fri, 10 Apr 2026 05:15:52 -0400 (EDT)
Newsgroups gmane.comp.boot-loaders.grub.bugs
Message-ID <[email protected]>
--8323329-1714636915-1775812552=:315045
Content-Type: TEXT/plain; CHARSET=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: inline

URL:=0A  <https://savannah.gnu.org/bugs/?68226>=0A=0A                 Summa=
ry: Problem with 64 bit bitmasks badram starting with=0A"f"=0A             =
      Group: GNU GRUB=0A               Submitter: masc=0A               Sub=
mitted: Fr 10 Apr 2026 09:15:47 UTC=0A                Category: Booting=0A =
               Severity: Major=0A                Priority: 5 - Normal=0A   =
           Item Group: Software Error=0A                  Status: None=0A  =
               Privacy: Public=0A             Assigned to: None=0A         =
Originator Name:=0A        Originator Email:=0A             Open/Closed: Op=
en=0A         Discussion Lock: Unlocked=0A                 Release: other=
=0A                 Release:=0A         Reproducibility: Every Time=0A     =
    Planned Release: None=0A=0A=0A    _____________________________________=
__________________=0A=0AFollow-up Comments:=0A=0A=0A-----------------------=
--------------------------------=0ADate: Fr 10 Apr 2026 09:15:47 UTC    By:=
 M <masc>=0AOne of my personal machines, non-ECC, started to have a broken =
memory area,=0Awhich I hoped to be able to mask easily using the GRUB_BADRA=
M setting.=0A=0AHowever, GRUB failed to boot after setting something like=
=0A=0Abadram 0x000000008c4e0800,0xffffffffffffcfe0=0A=0AJust black screen, =
thats it. Had to roll it back on the fs manually.=0A=0AI found this article=
=0Ahttps://unix.stackexchange.com/questions/746164/grub-hangs-itself-with-6=
4bit-memtest86-badram-pattern=0Awhich also contains the quick-fix.=0A=0Abad=
ram 0x000000008c4e0800,0x7fffffffffffcfe0=0A=0AAnd because of the unlikely =
situation that someone would have to mask that=0Amuch RAM, that will likely=
 never be a problem and thats likely also the reason=0Ait may have never ma=
de it into a bug report. For completeness' sake I wanted=0Ato make one anyw=
ay. Feel free to just abandon it.=0A=0AThis was tested with=0A=0AGRUB 2.14~=
git20250718.0e36779-1ubuntu4 on Ubuntu 25.10=0A=0A=0A=0A=0A=0A=0A=0A    ___=
____________________________________________________=0A=0AReply to this ite=
m at:=0A=0A  <https://savannah.gnu.org/bugs/?68226>=0A=0A__________________=
_____________________________=0ANachricht gesendet =C3=BCber Savannah=0Ahtt=
ps://savannah.gnu.org/=0A
--8323329-1714636915-1775812552=:315045
Content-Type: APPLICATION/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCadi/yAAKCRCqLAuaBUf3
Tld/AQDm+EjtbnMkqfg+bCwmNxwkzZHs1XZXozK1VhMCu0lElQD+MhGVITzQtPj1
4muZSR07kfm855rwDJOTEjRraBdzbwo=
=/Gnm
-----END PGP SIGNATURE-----

--8323329-1714636915-1775812552=:315045--