On 2023-09-11 11:28, Michel Dänzer wrote:

Package: grub-efi
Version: 2.12~rc1-9
Severity: important

After upgrading to 2.12~rc1, any boot entry hangs after 'Loading initial ramdisk ...'. I'll attach a photo showing the debug=all output when it hangs.

Downgrading to 2.06-13 avoids the issue.

Still the same issue with 2.12-1.

Is there any more information I can provide to help solve this? For the time being I can keep the system booting with 2.06-14, I suspect that won't be a reasonable option forever though.


--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Michel,

There are a rather high number of variables to isolate here. If you
could provide the following information, it might help provide a
better guess at what's going on:
- Computer (or mainboard if white box desktop) model
- Firmware revision
- Is Secure Boot enabled?
- Description of your disk layout

Also if you could just try using the grub 2.12-1 binary to boot a
kernel+initrd from an ext4 volume directly (e.g. using a usb drive or
spare disk), that would also be very helpful, I wonder if this
regression has something to do with LVM.

Mate

On Sun, Feb 18, 2024 at 3:16 PM Michel Dänzer <michel@daenzer.net> wrote:

On 2023-09-11 11:28, Michel Dänzer wrote:

Package: grub-efi
Version: 2.12~rc1-9
Severity: important

After upgrading to 2.12~rc1, any boot entry hangs after 'Loading initial ramdisk ...'. I'll attach a photo showing the debug=all output when it hangs.

Downgrading to 2.06-13 avoids the issue.

Still the same issue with 2.12-1.

Is there any more information I can provide to help solve this? For the time being I can keep the system booting with 2.06-14, I suspect that won't be a reasonable option forever though.

--
Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and Xwayland developer

_______________________________________________
Pkg-grub-devel mailing list
Pkg-grub-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grub-devel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Mate,


thanks for your follow-up.


On 2024-02-19 08:31, Mate Kukri wrote:

There are a rather high number of variables to isolate here. If you
could provide the following information, it might help provide a
better guess at what's going on:
- Computer (or mainboard if white box desktop) model

It's a Lenovo Thinkpad E595.

- Firmware revision

I upgraded to the latest 1.29, no change regarding this issue.

- Is Secure Boot enabled?

It's disabled.

- Description of your disk layout

It's a 512GB NVMe SSD. There are two partitions:

1. The EFI system partition (289MB)
2. A LUKS encrypted volume (rest)

The LUKS volume contains an LVM2 PV, with LVs for the root filesystem (which includes /boot) and swap.

Also if you could just try using the grub 2.12-1 binary to boot a kernel+initrd from an ext4 volume directly (e.g. using a usb drive or
spare disk), that would also be very helpful, I wonder if this
regression has something to do with LVM.

Before this I tried booting a Debian kernel image instead of a self-built one, and that booted fine. That seems to rule out an LVM or LUKS related issue. Should have tried this earlier. :(

My working theory is that it's due to some kernel build configuration change in my self-built kernels compared to Debian ones. I'll try narrowing it down, though if you happen to know of any kernel build configuration no longer supported with GRUB 2.12,
that might be helpful.


--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-03-08 11:44, Michel Dänzer wrote:

My working theory is that it's due to some kernel build configuration change in my self-built kernels compared to Debian ones.

My second guess was a winner: CONFIG_EFI_DISABLE_PCI_DMA breaks booting with GRUB 2.12 on this machine.

It works fine on two other (desktop) machines though, so the UEFI firmware seems to be a factor. OTOH it worked with GRUB 2.06 on this machine as well, so something changed in GRUB. Don't know if it's a bug though.


--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)