[Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

[Anthony Wong]

** Description changed:

  [Impact]
  This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
  
  The newer version of capsule flashing tools in Ubuntu 17.04 supports the
- reset type from some querycapsuleinfo call.
+ reset type from some querycapsuleinfo call：
  
  https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
+ 
+ fwupdate 9-1 has other bugfixes that are important too:
+  - some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
+   - some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
+   - some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
  
  [Test Case]
  
  == fwupdate ==
  On a system with a capsule update available, perform capsule update using fwupdate.  Verify the system works properly after the update.
  
  == fwupd ==
  The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
  
  To test, perform firmware update with fwupdmgr and see if it works.
  
  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
  
  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems.  This is actually a BIOS
  problem in those situations.
  
  It's unlikely that this should happen though because querying for reset
  types more closely aligns to the implementations that other OSes use
  when applying capsule updates.

** Description changed:

  [Impact]
- This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
+ This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
  
  The newer version of capsule flashing tools in Ubuntu 17.04 supports the
  reset type from some querycapsuleinfo call：
  
  https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
  
  fwupdate 9-1 has other bugfixes that are important too:
-  - some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
-   - some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
-   - some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
+  - some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
+   - some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
+   - some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
  
  [Test Case]
  
  == fwupdate ==
  On a system with a capsule update available, perform capsule update using fwupdate.  Verify the system works properly after the update.
  
  == fwupd ==
  The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
  
  To test, perform firmware update with fwupdmgr and see if it works.
  
  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
  
  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems.  This is actually a BIOS
  problem in those situations.
  
  It's unlikely that this should happen though because querying for reset
  types more closely aligns to the implementations that other OSes use
  when applying capsule updates.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupd package in Ubuntu:
  New
Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  New
Status in fwupdate source package in Xenial:
  In Progress
Status in fwupdate-signed source package in Xenial:
  In Progress
Status in fwupd source package in Yakkety:
  New
Status in fwupdate source package in Yakkety:
  In Progress
Status in fwupdate-signed source package in Yakkety:
  In Progress
Status in fwupd source package in Zesty:
  New
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  fwupdate 9-1 has other bugfixes that are important too:
   - some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
    - some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
    - some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using fwupdate.  Verify the system works properly after the update.

  == fwupd ==
  The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.

  To test, perform firmware update with fwupdmgr and see if it works.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems.  This is actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

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