[Bug 1716424] Please test proposed package

[Steve Langasek]

Hello Mathieu, or anyone else affected,

Accepted grub2-signed into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.13 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
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/1716424

Title:
  correctly parse PMEM memory ranges to pass it to the kernel

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in grub2 source package in Zesty:
  Triaged
Status in grub2-signed source package in Zesty:
  New
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]
  If trying to boot a system with PMEM:

  "Unknown memory type 14, considering reserved"

  The system will then not have access to EFIPresistentMemory ranges,
  because grub could not hand them over to the kernel to use. The
  resulting system would be missing a /dev/pmemN device.

  Grub requires 4 cherry-picked commits:

      - debian/patches/git_pmem_really_mark_mem_reserved_3d2c8048.patch
      - debian/patches/git_pmem_translate_persistent_type_76ce1de7.patch
      - debian/patches/git_pmem_mmap_handle_pmem_c79c59f1.patch
      - debian/patches/git_pmem_efiemu_handle_pmem_ae3b83a4.patch

  
  [Test case]
  - Boot PMEM-enabled system with updated grub

  [Regression Potential]
  This changes handling of memory ranges in grub, and may lead to incorrectly passing memory to the kernel, or otherwise allowing allocation of memory within reserved ranges. This would typically lead to a failure to boot the kernel, or missing memory-based devices (such a missing /dev/pmem0).

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