group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1716424@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.14

---------------
grub2 (2.02~beta2-36ubuntu3.14) xenial; urgency=medium

  * Add grub2/update_nvram template to allow users to disable NVRAM
    updates during package upgrades (LP: #1642298).

 -- dann frazier <dannf@xxxxxxxxxx>  Thu, 14 Sep 2017 16:13:39 -0600

** Changed in: grub2 (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

** Changed in: grub2-signed (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Released
Status in grub2-signed source package in Xenial:
  Fix Released
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