GRUB is responsible for loading the initrd into memory, so it is possible that 
this is a GRUB regression.  Also, this message is new to me:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
So maybe this is related to a new GRUB initrd loading method?

To test that, I grabbed focal's grubnetaa64.efi[*] and retested. This
actually worked, and contains no "LINUX_EFI_INITRD_MEDIA_GUID" messages
in the stub:

EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
[    0.000000] Booting Linux on physical CPU 0x0000120000 [0x413fd0c1]

So, adding a grub task.


[*] 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/uefi/grub2-arm64/2.04-1ubuntu26/grubnetaa64.efi.signed

** Attachment added: "howzit-iso-console+focal-grub.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5578349/+files/howzit-iso-console+focal-grub.log

** Also affects: grub2-unsigned (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to