[Bug 2044549] Re: pxe boot on arm64 stopped working

[Julian Andres Klode]

So the last upload only touched NTFS and device tree fix up protocol, it
shouldn't cause a regression here.

The one before that was prepared in February and released on Sep 29, and
includes additional memory management changes:

https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2004643

We initially heard from other vendor that they noticed some platforms
failing to boot, but there have been neither updates from them nor any
complaints in the over 3 months in proposed either, so I don't know.

In any case, the next steps for you would be to see if ubuntu14.2 works
or not.

If it's broken, iteratively unapply the last three patches until it
works to find the culprit.

If ubuntu14.2 is not broken, this is not a grub regression but a change
in your lab that is outside of our control.

If you have further questions do not hesitate to reach out in the ~uefi
channel on Mattermost.

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

Title:
  pxe boot on arm64 stopped working

Status in grub2 package in Ubuntu:
  New

Bug description:
  We have a lab with eight arm64 machines which are deployed from MAAS (also on arm64). 
  Two weeks ago we noticed the commissioning in MAAS is not working.
  We can see MAAS sends two files (bootaa64.efi and grubaa64.efi) as requested and then machine goes to grub prompt.
  @alexsander-souza from MAAS team had a look and he suspects grub issue. net_bootp command returns "error: couldn't send  network packet".
  Sometimes when machine is power cycled it can deploy again, but not always.
  Any idea how to debug this?

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