[Bug 1750351] Re: (Thinkpad T470) Boot loop after update

[Mathieu Trudel-Lapierre]

The packages themselves are not buggy. This appears to be an issue
caused by firmware doing exactly what it is told and designed to do.

I didn't notice that earlier, but there's a "Boot Order Lock" option in
Lenovo's firmware, and it is set to Enabled in the screenshots you
provided.

Automated boot fallback can only work if the BootOrder can be changed,
as that is what it used to let the system boot directly to disk, then
rebuild the 'ubuntu' entry, and reboot to get into it.

If you disable 'Boot Order Lock' and remove the hold on the packages, I
expect the system to successfully update, and boot to Ubuntu
successfully. At the very least, it will definitely help ensuring
fallback works without multiple reboot.

I'm still not sure if there isn't also a latent issue caused by NVMe,
but I think this will get us one step in the right direction :)

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

Title:
  (Thinkpad T470) Boot loop after update

Status in shim package in Ubuntu:
  Incomplete

Bug description:
  After upgrading shim-signed to 1.33.1~17.10.1 (and installing the grub
  updates that were published at the same time), the system is stuck in
  a boot loop. I've had to downgrade shim and grub to their release
  versions to get the system to boot again.

  The following message gets displayed before the system resets each time:
  > System BootOrder not found. Initializing defaults.
  > Creating boot entry "Boot0000" with label "ubuntu" for file "\EFI\ubuntu\shim64.efi"
  >
  > Reset system

  A similar message, without the last line, was already displayed on
  successful boots before the update.

  According to the information in bug #1747889, the Thinkpad X1 Carbon
  might be affected as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shim 0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 11:10:34 2018
  Dependencies:
   
  EFITables:
   Feb 19 10:08:21 mdbauman kernel: efi: EFI v2.50 by Lenovo
   Feb 19 10:08:21 mdbauman kernel: efi:  SMBIOS=0xba69b000  SMBIOS 3.0=0xba698000  ACPI=0xbb5fe000  ACPI 2.0=0xbb5fe014  MEMATTR=0xb4a1f298 
   Feb 19 10:08:21 mdbauman kernel: Secure boot enabled and kernel locked down
   Feb 19 10:08:21 mdbauman kernel: Bluetooth: hci0: Secure boot is enabled
   Feb 19 10:18:41 mdbauman fwupd[2852]: disabling plugin because: failed to coldplug uefi: UEFI firmware updating not supported
  InstallationDate: Installed on 2017-09-09 (162 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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