This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1755624

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755624

Title:
  With intel-microcode 3.20180312, kernel reports as broken spectre v2
  microcode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With an intel-microcode package based off of
  https://downloadcenter.intel.com/download/27591/Linux-Processor-
  Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic
  reports the following in dmesg:

  [    0.000000] microcode: microcode updated early to revision 0x84, date = 
2018-01-21
  [    0.000000] Intel Spectre v2 broken microcode detected; disabling 
Speculation Control

  And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo.
  Other testers of the updated microcode report seeing the same thing.

  The processor this is being tested on is:

  cpu family      : 6
  model           : 142
  model name      : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  stepping        : 9
  microcode       : 0x84

  The test for the microcode is in https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178
  ; specifically, it looks like bad_spectre_microcode(c) is returning
  true.

  It seems
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc
  has not been pulled in yet (though it's staged as
  3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is
  in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby
  Lake processors, but other processers may need to be verified for
  correctness.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to