touch-packages team mailing list archive

[Henrique de Moraes Holschuh <1386257@xxxxxxxxxxxxxxxxxx>]

You will want the newer intel-microcode packages, then.   This means a
resync with Debian is highly advised.

Exactly due to the issue brought to the front by the Intel Haswell
microcode update that disabled TSX, Debian has switched to enforcing
that automated microcode updates be done only through the early
initramfs.  This, in fact, requires a reboot to apply the microcode
update (just like a kernel update).

While I did blacklist the offending Haswell microcode updates in the
Debian packages so that they will not be applied by accident using the
late microcode driver (which results in an unusable system as described
in #1370352), this kind of blacklisting is reactive, so the switch to
early microcode updates is the only safe way forward right now.

Of course, it took ~10 years for the first Intel microcode update that
had visible effects at the ISA level to show up, so it might be another
10 years before the next one...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1386257

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions