I should also mention that we will be following Debian's lead and not
updating this for Trusty.  Lack of early upload being one of the big
reasons for this.

** Description changed:

  * A security fix has been made available as part of intel-microcode
  * It is advisable to apply it
  * Thus an SRU of the latest intel-microcode is desirable for all stable 
  [Test Case]
  * Upgrade intel-microcode package, if it is already installed / one is
  running on Intel CPUs
  * Reboot and verify no averse results, and/or that microcode for your
- cpu was loaded by expecting
+ cpu was loaded as expected.
  [Test case reporting]
  * Please paste the output of:
  dpkg-query -W intel-microcode
  grep -E 'model|stepping' /proc/cpuinfo | sort -u
  journalctl -k | grep microcode
  [Regression Potential]
  Microcode are proprietary blobs, and can cause any number of new errors and 
regressions. Microcode bugs have been reported before, therefore longer than 
usual phasing and monitoring of intel-microcode bugs should be done with extra 
+ [Other]
+ caml discussion describing test case to reproduce the crash.
+ https://caml.inria.fr/mantis/view.php?id=7452
+ =========================================================================
  [Original bug report]
  NB: I am *not* directly affected by this bug.
  Henrique emailed a warning to Debian devel today [1] on a potentially
  serious issue with (sky|kaby)lake processors. Excerpt:
  "This warning advisory is relevant for users of systems with the Intel
  processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
  7th generation Intel Core processors (desktop, embedded, mobile and
  HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
  well as select Intel Pentium processor models.
  TL;DR: unfixed Skylake and Kaby Lake processors could, in some
  situations, dangerously misbehave when hyper-threading is enabled.
  Disable hyper-threading immediately in BIOS/UEFI to work around the
  problem.  Read this advisory for instructions about an Intel-provided
  It is probably a good idea to:
  (1) issue a warning to our users about this;
  (2) update intel-microcode on all our supported releases
  I leave the discussion on whether this can have security implications to
  [1] https://lists.debian.org/debian-devel/2017/06/msg00308.html
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: intel-microcode 3.20161104.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Jun 25 10:14:19 2017
  InstallationDate: Installed on 2017-05-26 (30 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: intel-microcode (Ubuntu Trusty)
       Status: Confirmed => Won't Fix

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  intel-microcode is out of date, version 20170511 fixes errata on 6th
  and 7th generation platforms

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to