[Bug 1830123] Re: intel-microcode 20190514 does not provide Sandy Bridge (sigs 0x000206d7 and 0x000206d6)

Tyler Hicks tyhicks at canonical.com
Wed Jun 19 05:16:03 UTC 2019


On 2019-06-19 04:40:20, Wenhan Shi wrote:
> Do we have a timeline about when Intel will fix this bug?

No, the bug fixing process isn't that predictable. They are actively
working on it and they're occasionally providing status updates in the
upstream bug report:

  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
Files/issues/1

The most recent update is here:

  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
Files/issues/1#issuecomment-500457763


** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #1
   https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

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

Title:
  intel-microcode 20190514 does not provide Sandy Bridge (sigs
  0x000206d7 and 0x000206d6)

Status in intel-microcode package in Ubuntu:
  Confirmed

Bug description:
  Intel is still working on Sandy Bridge microcode (sigs 0x000206d7 and
  0x000206d6) to address MDS. This bug report is for people to track
  their status in Ubuntu.

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



More information about the foundations-bugs mailing list