Public bug reported:

Similar to bug 1642298, bug 1750732 and bug 1788539
This issue was only spotted on ThunderX Cavium ARM64 system in this SRU cycle. 
It works fine with ARM64 moonshot, and other X86 systems.
(I will check on that AMD Naples later)

Steps:
1. Deploy the ThunderX system with Trusty + X-HWE kernel
2. Check the efibootmgr output
3. Enable proposed, install grub-common
4. Check efibootmgr again

Result:
In step 2, the boot order is correct:
ubuntu@wright-kernel:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 10 seconds
BootOrder: 0002,0000,0003,0004,0001
Boot0000* ubuntu
Boot0001  UEFI: Built-in EFI Shell
Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

But in step 4, the boot order will be overridden:
ubuntu@wright-kernel:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 10 seconds
BootOrder: 0000,0002,0003,0004,0001
Boot0000* ubuntu
Boot0001  UEFI: Built-in EFI Shell
Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grub-common 2.02~beta2-9ubuntu1.15
ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140
Uname: Linux 4.4.0-134-generic aarch64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: arm64
Date: Tue Sep  4 07:45:19 2018
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug arm64 package-from-proposed trusty uec-images

** Summary changed:

- The proposed grub package in Trusty overrides the boot order on a MaaS 
deployed system
+ The proposed grub package in Trusty overrides the boot order on a MaaS 
deployed ThunderX system

** Description changed:

  Similar to bug 1642298, bug 1750732 and bug 1788539
- This issue was only spotted on ThunderX Cavium ARM64 system in this SRU cycle.
+ This issue was only spotted on ThunderX Cavium ARM64 system in this SRU 
cycle. It works fine with ARM64 moonshot, and other X86 systems.
  (I will check on that AMD Naples later)
  
  Steps:
  1. Deploy the ThunderX system with Trusty + X-HWE kernel
  2. Check the efibootmgr output
  3. Enable proposed, install grub-common
  4. Check efibootmgr again
  
  Result:
  In step 2, the boot order is correct:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: 0002,0000,0003,0004,0001
  Boot0000* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC
  
  But in step 4, the boot order will be overridden:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: 0000,0002,0003,0004,0001
  Boot0000* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grub-common 2.02~beta2-9ubuntu1.15
  ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-134-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: arm64
  Date: Tue Sep  4 07:45:19 2018
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  The proposed grub package in Trusty overrides the boot order on a MaaS
  deployed ThunderX system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to