Default to early instead of auto if MODULES=most

Tested on intel locally, it's loaded, with both amd64-microcode & intel-microcode installed from proposed.

ditto on amd baremetal instance i got off a public cloud.

This bug was fixed in the package intel-microcode - 3.20180425.1ubuntu1

---------------
intel-microcode (3.20180425.1ubuntu1) cosmic; urgency=medium

  * Default to early instead of auto, and install all of the microcode,
    not just the one matching the current CPU, if MODULES=most is set
    in the initramfs-tools config (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:31:30 +0200

This bug was fixed in the package amd64-microcode - 3.20180524.1ubuntu1

---------------
amd64-microcode (3.20180524.1ubuntu1) cosmic; urgency=medium

  * Default to 'early' instead of 'auto' in the initramfs-tools hook
    when building with MODULES=most (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:32:22 +0200

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.

Hello Julian, or anyone else affected,

Accepted intel-microcode into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-microcode/3.20180425.1~ubuntu0.18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted amd64-microcode into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted intel-microcode into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-microcode/3.20180425.1~ubuntu0.17.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted amd64-microcode into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.17.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted intel-microcode into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-microcode/3.20180425.1~ubuntu0.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted amd64-microcode into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted intel-microcode into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-microcode/3.20180425.1~ubuntu0.14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Julian, or anyone else affected,

Accepted amd64-microcode into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

btw. is it necessary for these to go to -security as well? Or just -updates is enough? For now I assumed the latter, since no security sign-off was requested (and for -security updates we'd need to get these built in the security PPA probably).

Hi, the trusty amd64-microcode SRU has been superceded by https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.14.04.2+really20130710.1 which was a revert due to LP: #1779092. Thanks.

Verified on xenial:

Get:15 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 intel-microcode amd64 3.20180425.1~ubuntu0.16.04.2 [1145 kB]
Get:16 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 amd64-microcode amd64 3.20180524.1~ubuntu0.16.04.2 [32.2 kB]

Checked update-initramfs -v output to check that both amd64 and intel microcode are installed, also checked that intel picks all microcode packets.

Same for bionic with:

Get:17 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 intel-microcode amd64 3.20180425.1~ubuntu0.18.04.2 [1143 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 amd64-microcode amd64 3.20180524.1~ubuntu0.18.04.2 [32.3 kB]

This bug was fixed in the package amd64-microcode - 3.20180524.1~ubuntu0.16.04.2

---------------
amd64-microcode (3.20180524.1~ubuntu0.16.04.2) xenial; urgency=medium

  * Default to 'early' instead of 'auto' in the initramfs-tools hook
    when building with MODULES=most (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:32:22 +0200

The verification of the Stable Release Update for amd64-microcode has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package intel-microcode - 3.20180425.1~ubuntu0.16.04.2

---------------
intel-microcode (3.20180425.1~ubuntu0.16.04.2) xenial; urgency=medium

  * Default to early instead of auto, and install all of the microcode,
    not just the one matching the current CPU, if MODULES=most is set
    in the initramfs-tools config (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:31:30 +0200

This bug was fixed in the package intel-microcode - 3.20180425.1~ubuntu0.18.04.2

---------------
intel-microcode (3.20180425.1~ubuntu0.18.04.2) bionic; urgency=medium

  * Default to early instead of auto, and install all of the microcode,
    not just the one matching the current CPU, if MODULES=most is set
    in the initramfs-tools config (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:31:30 +0200

This bug was fixed in the package amd64-microcode - 3.20180524.1~ubuntu0.18.04.2

---------------
amd64-microcode (3.20180524.1~ubuntu0.18.04.2) bionic; urgency=medium

  * Default to 'early' instead of 'auto' in the initramfs-tools hook
    when building with MODULES=most (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:32:22 +0200

Hello Julian, or anyone else affected,

Accepted amd64-microcode into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/amd64-microcode/3.20180524.1~ubuntu0.14.04.2+really20130710.1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

trusty before:
[...]
Calling hook amd64_microcode
Calling hook compcache
[...]
Calling hook intel_microcode
intel-microcode: adding microcode for currently online and selected Intel processors
intel-microcode: using early initramfs microcode update mode...
[...]

(that is, no amd, only current intel)

install versions from proposed:
[...]
Unpacking amd64-microcode (3.20180524.1~ubuntu0.14.04.2+really20130710.1ubuntu1) over (3.20180524.1~ubuntu0.14.04.2+really20130710.1) ...
Unpacking intel-microcode (3.20180425.1~ubuntu0.14.04.2) over (3.20180425.1~ubuntu0.14.04.1) ...
[...]

then:
Calling hook amd64_microcode
amd64-microcode: installing all microcode datafiles for AMD64 processors
amd64-microcode: installing AMD64 processor microcode update support into initramfs...
[...]
Calling hook intel_microcode
intel-microcode: adding microcode for either all or selected Intel processor models
intel-microcode: using early initramfs microcode update mode...

lsinitramfs here also shows microcode for both:
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/GenuineIntel.bin
[...]
lib/firmware/amd-ucode
lib/firmware/amd-ucode/microcode_amd.bin
lib/firmware/amd-ucode/microcode_amd_fam15h.bin

(note that trusty does not have early microcode loading for amd, only for intel).

This bug was fixed in the package intel-microcode - 3.20180425.1~ubuntu0.14.04.2

---------------
intel-microcode (3.20180425.1~ubuntu0.14.04.2) trusty; urgency=medium

  * Default to early instead of auto, and install all of the microcode,
    not just the one matching the current CPU, if MODULES=most is set
    in the initramfs-tools config (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 26 Jun 2018 16:31:30 +0200

This bug was fixed in the package amd64-microcode - 3.20180524.1~ubuntu0.14.04.2+really20130710.1ubuntu1

---------------
amd64-microcode (3.20180524.1~ubuntu0.14.04.2+really20130710.1ubuntu1) trusty; urgency=medium

  * Install (all) microcode on non-amd systems too if MODULES=most in initramfs-tools
    config (LP: #1778738)

 -- Julian Andres Klode <email address hidden> Tue, 07 Aug 2018 14:09:42 +0200