keep grub 2.06 in proposed

Bug #1953490 reported by Julian Andres Klode
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Undecided
Unassigned
grub2-signed (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Let's try to do some more testing with the signed images and all.

tags: added: block-proposed
Revision history for this message
Derk Willem te Bokkel (dtebokkel) wrote :

FYI Jammy-proposed testing issues

grub-efi-amd64-bin/jammy-proposed,now 2.06-2ubuntu2 amd64 [installed]
  GRand Unified Bootloader, version 2 (EFI-AMD64 modules)

grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
  GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)

note when these are installed ..they can not find the kernel on any linux root partition
(multiboot system)

reverting to a previous version if functional

Revision history for this message
Derk Willem te Bokkel (dtebokkel) wrote :
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Julian, Derk,

I have been testing grub2-2.06-2ubuntu2 in -proposed in KVM, on both BIOS and EFI VMs, and both appear to be broken.

On BIOS, grub2 doesn't get installed automatically, so I have to manually run "grub-install /dev/vda". When I do, I reboot into grub 2.06, and upon selecting a kernel, I see:

error: premature end of file /vmlinuz-5.15.0-13-generic.
error: you need to load the kernel first.

Press any key to continue...

On EFI, shim-signed installs grub 2.06, but when I reboot and select a kernel, I see:

error: out of memory.
error: you need to load the kernel first.

Press any key to continue...

EFI stub: ERROR: Failed to allocate usable memory for kernel.
EFI stub: ERROR: efi_relocate_kernel() failed!
EFI stub: ERROR: efi_main() failed!
BdsDxe: failed to start Boot0004 "ubuntu" from HD(1,GPT,7165AAF-9AAE-4CD2-AEBC-6A8854B86CCD,0x800,0x100000)/\EFI\ubuntu\shimx64.efi: Not Found

I press enter, then:

ERROR
Could not install security protocol: (0x2) Invalid Parameter
OK
Something has gone seriously wrong: Invalid Parameter
shim cannot continue, sorry.

Both VMs fail to boot, causing this grub update to be a regression.

Revision history for this message
Julian Andres Klode (juliank) wrote :

I can confirm the issue with the VM. Enabling debugging makes things work again (set debug=all), which is sad. Needs further investigation.

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Julian,

I have tested grub 2.06-2ubuntu3 in both BIOS and EFI mode on VMs, and I can confirm that your patches have fixed both of the issues I was seeing.

Thanks for the quick turnaround! I will keep testing these packages, but it all seems good under secureboot.

Thanks,
Matthew

Revision history for this message
Julian Andres Klode (juliank) wrote :

The reported regressions are all fixed, and I have finished validating reboots in the autopkgtest-cloud.

We are still unable to secure boot on arm64 (bug 1954683). But as this is not strictly a regression (the userspace grub-check-signatures always failed and prevented installation of grub, now additionally it fails to actually verify kernels at boot), I'm not going to block on it.

Changed in grub2 (Ubuntu):
status: New → Fix Released
Changed in grub2-signed (Ubuntu):
status: New → Fix Released
tags: removed: block-proposed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.