One hypothesis is that the network stack/UEFI driver dies after loading the initial GRUB image. To test that, I started a ping at the server until it dropped to the GRUB prompt. Now, I never saw a single ping response - even while the server was successfully TFTP'ing GRUB from MAAS. Maybe it just has ping responses disabled. But what I did notice is that the GRUB process, which is sitting at a `grub>` prompt, becomes unresponsive while the system is being pinged.
The failing system happens to have 2 models of NICs in it - Intel and Mellanox. I happen to be seeing this with the Intel NIC. I'll try to get a Mellanox one wired up to see if the issue follows the NIC model. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934192 Title: regression between 2.04-1ubuntu44 and 2.04-1ubuntu44.2 breaks netboot on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1934192/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
