The jammy RC (20220418.2) looks good for Ampere Mt. Jade Altra (bizzy).
I can pxe install the server successfully.
By the way autoinstall of subiquity also works like a charm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2-signed (Ubuntu Jammy)
Status: New => Fix Released
--
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
This bug was fixed in the package grub2 - 2.06-2ubuntu7
---
grub2 (2.06-2ubuntu7) jammy; urgency=medium
[ Heinrich Schuchardt ]
* Disable LOAD FILE2 protocol for initrd on ARM (LP: #1967562)
-- dann frazier Fri, 15 Apr 2022 15:50:11 -0600
** Changed in: grub2 (Ubuntu Jammy)
reported upstream: https://lists.gnu.org/archive/html/grub-
devel/2022-04/msg00055.html
--
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
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Invalid
--
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.
** Merge proposal linked:
https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407
--
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
** Also affects: grub2 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Incomplete
** Also affects: grub2-signed (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu
** Tags removed: rls-jj-incoming
--
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
As long as the kernel stub does not invoke the SNP protocol itself it is
safe for GRUB to assume that it is still in a good state when reaching
the Load File2 protocol call.
I am not aware of any requirement in the UEFI specification to leave the
network adapter in a specific state on
As we are close to release date we should simply disable Load File2 protocol on
ARM in Jammy:
https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well spotted Heinrich. I'd hypothesized that something was shutting down
the network stack, but didn't yet no where to look, and overlooked
grub_net_fini_hw() message! With that hint, I went ahead and tried
commenting out[*] the registration of that callback, and voila, the
ReadFile2 initramfs
As the log below shows grub_net_fini_hw() is called before entering the
kernel and before the LoadFile2 protocol is executed:
loader/efi/linux.c:478: kernel @ 0xf63d8000
net/net.c:1559: fs_close() name: /casper/vmlinuz
net/net.c:1510: fs_open() name: /casper/initrd
loader/efi/linux.c:396:
** No longer affects: grub2-unsigned (Ubuntu)
--
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
On riscv64 we cannot boot without the LoadFile2 protocol. So the short
term fix of forcing to 0 must be architecture specific. Check for
__riscv not defined.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: fr-2245
--
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
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967562
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Milestone: None => ubuntu-22.04
** Changed in: grub2-signed (Ubuntu)
Milestone: None =>
Since it seems a grub issue, I reported the issue to qatracker of daily
build to make the release team aware of this issue, and hopefully the
information will be helpful before releasing RC.
http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246802/testcases/1697/results
--
You received
I randomly picked another ARM server, a Cavium ThunderX system, and it
also fails to net boot w/ jammy's GRUB, but works fine w/ the patch in
comment #16. So this is looking like possibly an architecture-wide
issue. I tested on an x86 VM, but I didn't see any of the LoadFile2
messages. I assume
Removing efi-implement-grub_efi_run_image.patch didn't avoid the
problem, nor did removing both that and efi-implemented-
LoadFile2-initrd-loading-protocol-fo.patch, but that appears to just be
because the arm64 code gets migrated to the efi loader code later in the
series, basically reintroducing
Though maybe you also need to unapply efi-implemented-LoadFile2-initrd-
loading-protocol-fo.patch
--
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
To figure out if it's the new loader code, remove efi-implement-
grub_efi_run_image.patch (or the grub-core/loader/efi/linux.c hunk) or
enable secure boot (if available). The new code path on insecure systems
uses the upstream loader + LoadFile2 support, as is necessary for
RISC-V.
--
You
I turned on grub debugging (set debug=all in grub.cfg), and this seems
interesting. The "error: couldn't send network packet." message may
actually be telling us something is wrong with downloading the initrd.
Full log attached, here's a filtered version:
[...]
loader/efi/linux.c:80: UEFI stub
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
The iso-booted-kernel has no problem unpacking the initramfs:
[ 15.282839] Trying to unpack rootfs image as initramfs...
[...]
[ 15.935483] Freeing initrd memory: 103248K
But that's interesting, the freed initrd memory size reported is
different here. When PXE-booted, it was 103244K. 103248K
I can reproduce, and I've attached the full console log (!quiet,
+debug). Here's some interesting pieces of the log:
EFI stub: Booting Linux Kernel...
EFI stub: Generating empty DTB
error: couldn't send network packet.
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub:
** Summary changed:
- jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
+ jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo
