That makes sense. The commit doesn't revert cleanly but before finding the
option I just reverted the default:
diff --git a/grub-core/term/serial.c b/grub-core/term/serial.c
index 8260dcb7a..72a6927b4 100644
--- a/grub-core/term/serial.c
+++ b/grub-core/term/serial.c
@@ -271,7 +271,7 @@
So I spent an evening bisecting the issue from upstream sources.
The problem was introduced with
> 7b192ec4c term/ns8250: Use ACPI SPCR table when available to configure serial
The old behaviour can be regained by setting the unit explicitly grub.cfg
> serial --unit=0 --speed=115200
This solves
more
> likely we can do something about this.
>
> Also I'll take a quick look at what code is in the GRUB image at the
> crashing offset, but I suspect that won't be enough information to
> workaround this.
>
> Mate
>
> On Wed, Jan 31, 2024 at 9:29 AM Morten Hein T
several similar machines, so I suspect a
software regression rather than a hardware issue.
FWIW the EFI BIOS is
American Megatrends
Version 2.20.1276
Core Version 5.14
I realize that this is not a lot to go on, but I would appreciate any
hints on how to debug this issue.
Best,
Morten Hein Tiljeset
> I'm afraid touching the memory management system in the 2.06 grub in
> stable releases is out of the question. The fixes involve a ton of
> patches and it's not really possible to cherry-pick them and the risk
> of regression is significant and out of scope for (only) a stable
> release.
>
> The
ssue.
I've also tried to backport grub 2.06-13+deb12u1 from bookworm, but this
does not help. I hence believe this problem affects both Debian
bullseye and bookworm.
Best,
Morten Hein Tiljeset
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/nvme0n1p1 / ext4 rw,noat
6 matches
Mail list logo
