Accepted intel-microcode 3.20161104.1~bpo8+1 (amd64 i386 source) into jessie-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 13 Nov 2016 20:31:01 -0200
Source: intel-microcode
Binary: intel-microcode
Architecture: amd64 i386 source
Version: 3.20161104.1~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Henrique de Moraes Holschuh <hmh@debian.org>
Changed-By: Henrique de Moraes Holschuh <hmh@debian.org>
Description:
intel-microcode - Processor microcode firmware for Intel CPUs
Changes:
intel-microcode (3.20161104.1~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports (no changes)
.
intel-microcode (3.20161104.1) unstable; urgency=medium
.
* New upstream microcode datafile 20161104
+ New Microcodes:
sig 0x00050663, pf_mask 0x10, 2016-10-12, rev 0x700000d, size 20480
sig 0x00050664, pf_mask 0x10, 2016-06-02, rev 0xf00000a, size 21504
+ Updated Microcodes:
sig 0x000306f2, pf_mask 0x6f, 2016-10-07, rev 0x0039, size 32768
sig 0x000406f1, pf_mask 0xef, 2016-10-07, rev 0xb00001f, size 25600
+ Removed Microcodes:
sig 0x000106e4, pf_mask 0x09, 2013-07-01, rev 0x0003, size 6144
+ This update fixes critical errata on Broadwell-DE V2/Y0 (Xeon
D-1500 family), including one that can crash VMWare ESXi 6 with
#PF (VMWare KB2146388), and could affect Linux as well. This same
issue was fixed for the E5v4 Xeons in release 20160607
+ This update fixes undisclosed (and likely critical) errata on
Broadwell-E Core i7-68xxK/69xxK/6950X, Broadwell-EP/EX B0/R0/M0
Xeon E5v4 and Xeon E7v4, and Haswell-EP Xeon E5v3
+ This release deletes the microcode update for the Jasper Forest
embedded Xeons (Xeon EC35xx/LC35xx/EC35xx/LC55xx), for undisclosed
reasons. The deleted microcode is outdated when compared with the
updates for the other Nehalem Xeons
* Makefile: always exclude microcode sig 0x206c2 just in case
Intel is quite clear in the Intel SA-00030 advisory text that recent
revisions (0x14 and later?) of the 0x206c2 microcode updates must be
installed along with updated SINIT ACM on vPro systems (i.e. through
an UEFI/BIOS firmware update). This is a defensive change so that we
don't ship such a microcode update in the future by mistake
* source: remove partially superseded upstream data file: 20160714
* source: remove superseded upstream data file: 20101123
* changelog: replace "pf mask" with "pf_mask"
* control, compat: switch debhelper compatibility level to 9
* control: bump standards-version, no changes required
Checksums-Sha1:
8c146e591ddc3a3ab396df495e7cc4d39314377d 1811 intel-microcode_3.20161104.1~bpo8+1.dsc
faa4a231f15053e00ab15869b2231e34572ca403 1184876 intel-microcode_3.20161104.1~bpo8+1.tar.xz
b7447f89d77879b862d07e4b493be4d7fc2f446c 696330 intel-microcode_3.20161104.1~bpo8+1_amd64.deb
d36981b4d5037f29cfc3240c5cbc67e8a38818c3 837040 intel-microcode_3.20161104.1~bpo8+1_i386.deb
Checksums-Sha256:
afb4103a318e6f25f30ecca740dbcf8e58f252ac6613822a73b4bb248661082b 1811 intel-microcode_3.20161104.1~bpo8+1.dsc
20a5a8d2dc8b5b7a48cfa51119073c1a28a9f8c6931eee06efd885746c62d157 1184876 intel-microcode_3.20161104.1~bpo8+1.tar.xz
cd06a12e30862749e36344d0ddbab89129b8be12f88b0baf58662b46f85b938f 696330 intel-microcode_3.20161104.1~bpo8+1_amd64.deb
298320325038c2e91b99bd84d3ab0c100f0c7778a28da1aa94cb28d75d28a08d 837040 intel-microcode_3.20161104.1~bpo8+1_i386.deb
Files:
f2c9e64c23eedac58ad32a55b1c5e06e 1811 non-free/admin standard intel-microcode_3.20161104.1~bpo8+1.dsc
4215758541cde3f8e97ff20d9e9efc2b 1184876 non-free/admin standard intel-microcode_3.20161104.1~bpo8+1.tar.xz
d2f8e5454a5d35c7e2a13e70f5054860 696330 non-free/admin standard intel-microcode_3.20161104.1~bpo8+1_amd64.deb
37c9b34982eaf15b4cd655e7c34bdb9f 837040 non-free/admin standard intel-microcode_3.20161104.1~bpo8+1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJYKOsiAAoJEP4Rv6aLFY6YkmkQAI5VJ456hdAaQ9WYxVuUwW52
4AigBWyoOWAXUhU3JuUpgArPQiYlo22cumNIaFeO3zMeUscXVIh3gca/z+i4/8D5
tjbNEP4v7N92Yn1N2FbPFtXE5BLq5+DrceFUGSGk+BEfjFmFkB5H7rXzivakS7Y9
0XPYwPlm3wNguI3TfvGa1LlGaOSSxbChAi4MtmXnOY2uQX0QwEq5sW+fBidT8c9m
T7cBH6X/FEJJkdOAsYHTXFnOFGjEbkajj3dfeKROeXdEa4CLj2HC2JB865KwtHLA
dbuvgu7C9eFYVh/VvPYcqH/oGLjoTVh+lgfO/S8RjCuTc0rHc9iEFFkW7alK5vT2
Elcjbo3jQmHBFQEIjYDBH3S0HdRbON7Bo3JXEWIcy1GLRBMNOxxUSeEQL6cnLUyW
TBRPCXH2neOtPCB2RmCi2KCho8NW2ztb53fl0alLY9KvfqPZjrsUBXEB1ib97pIT
B2nOBC/tNBoiA/BL7m9bBEumEXWjIxqRn2RRm7Ge6D+vSFSkFumEzNvr3cacosJM
AOuizJX5FYqFMrMiiBUkotbccAoE3VXibpoywsUg03MbCNuAux6snaa5iX0QIpd+
AtzWaXV67Pmd9by3vTwez3Hl3wDiM+6VYWPZIweRXmh3RzTPhlZ1+iZywKLL4sxT
3liAt9y4HKKkyReXGXWn
=eQ8K
-----END PGP SIGNATURE-----
Reply to: