[Bug 1778738] Re: Default to early instead of auto when MODULES=most

[Julian Andres Klode]

I'm not sure how feasible retesting loading of the firmware is for the 8
SRUs. We tested that once on cosmic per vendor, so given that the rest
is equal, just ensuring it's there is probably fine.

** Description changed:

  [Impact]
  Initramfs for MODULES=most should build with all microcodes installed
  
  [Test case]
  Have both amd64-microcode and intel-microcode installed, and MODULES=most set. Test generated initramfs in both amd64 and intel machines and make sure the microcodes load.
  
+ If that's not feasible, we should at least run update-initramfs with -v
+ and ensure that it says the right things:
+ 
+ intel-microcode: adding microcode for either all or selected Intel processor models
+ [long list of microcodes]
+ 
+ and that lsinitramfs tells us about
+ 
+ kernel/x86/microcode/AuthenticAMD.bin
+ 
+ 
  [Regression potential]
  Some tools will fail to understand the initramfs, as it now has two cpio archives prepended (e.g. lsinitramfs skips intel microcode archive, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886424)

** Description changed:

  [Impact]
  Initramfs for MODULES=most should build with all microcodes installed
  
  [Test case]
  Have both amd64-microcode and intel-microcode installed, and MODULES=most set. Test generated initramfs in both amd64 and intel machines and make sure the microcodes load.
  
  If that's not feasible, we should at least run update-initramfs with -v
  and ensure that it says the right things:
  
+ I: amd64-microcode: installing AMD64 microcode into the early initramfs...              
  intel-microcode: adding microcode for either all or selected Intel processor models
  [long list of microcodes]
- 
- and that lsinitramfs tells us about
- 
- kernel/x86/microcode/AuthenticAMD.bin
  
  
  [Regression potential]
  Some tools will fail to understand the initramfs, as it now has two cpio archives prepended (e.g. lsinitramfs skips intel microcode archive, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886424)

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

Title:
  Default to early instead of auto when MODULES=most

Status in amd64-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode package in Ubuntu:
  Fix Released
Status in amd64-microcode source package in Trusty:
  New
Status in intel-microcode source package in Trusty:
  New
Status in amd64-microcode source package in Xenial:
  New
Status in intel-microcode source package in Xenial:
  New
Status in amd64-microcode source package in Artful:
  New
Status in intel-microcode source package in Artful:
  New
Status in amd64-microcode source package in Bionic:
  New
Status in intel-microcode source package in Bionic:
  New

Bug description:
  [Impact]
  Initramfs for MODULES=most should build with all microcodes installed

  [Test case]
  Have both amd64-microcode and intel-microcode installed, and MODULES=most set. Test generated initramfs in both amd64 and intel machines and make sure the microcodes load.

  If that's not feasible, we should at least run update-initramfs with
  -v and ensure that it says the right things:

  I: amd64-microcode: installing AMD64 microcode into the early initramfs...              
  intel-microcode: adding microcode for either all or selected Intel processor models
  [long list of microcodes]

  
  [Regression potential]
  Some tools will fail to understand the initramfs, as it now has two cpio archives prepended (e.g. lsinitramfs skips intel microcode archive, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886424)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1778738/+subscriptions