[Bug 1508893] Re: TFTP timeout when booting from grub that was PXE loaded
Launchpad Bug Tracker
1508893 at bugs.launchpad.net
Thu Dec 10 18:13:19 UTC 2015
This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.5
---------------
grub2 (2.02~beta2-9ubuntu1.5) trusty; urgency=medium
* d/p/arm64-set-correct-length-of-device-path-end-entry.patch: Fixes
booting arm64 kernels on certain UEFI implementations. (LP: #1476882)
* progress: avoid NULL dereference for net files. (LP: #1459872)
* arm64/setjmp: Add missing license macro. (LP: #1459871)
* Cherry-pick patch to add SAS disks to the device list from the ofdisk
module. (LP: #1517586)
* Cherry-pick patch to open Simple Network Protocol exclusively.
(LP: #1508893)
-- dann frazier <dannf at ubuntu.com> Wed, 25 Nov 2015 13:13:35 -0700
** Changed in: grub2 (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
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/1508893
Title:
TFTP timeout when booting from grub that was PXE loaded
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2 source package in Trusty:
Fix Released
Status in grub2 source package in Vivid:
Fix Committed
Status in grub2 source package in Wily:
Fix Committed
Bug description:
[Impact]
PXE booting of UEFI systems is very slow, to the point that some systems timeout.
[Test Case]
PXE boot a UEFI-based system (d-i or MAAS) and monitor the time it takes for GRUB to download the kernel/initrd. tcpdump will show TFTP timeouts, and it can take on the order of minutes to begin running the kernel.
[Regression Risk]
The fix is restricted to UEFI-based systems. For those systems, it could lead to a regression if Managed Network Protocol is required to remain active while GRUB is performing the network boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions
More information about the foundations-bugs
mailing list