Accepted intel-microcode 3.20171117.1~bpo9+1 (amd64 i386 source) into stretch-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 26 Nov 2017 11:00:28 -0200
Source: intel-microcode
Binary: intel-microcode
Architecture: amd64 i386 source
Version: 3.20171117.1~bpo9+1
Distribution: stretch-backports
Urgency: high
Maintainer: Henrique de Moraes Holschuh <hmh@debian.org>
Changed-By: Henrique de Moraes Holschuh <hmh@debian.org>
Closes: 828819 862606
Description:
intel-microcode - Processor microcode firmware for Intel CPUs
Changes:
intel-microcode (3.20171117.1~bpo9+1) stretch-backports; urgency=medium
.
* Rebuild for stretch-backports (no changes)
.
intel-microcode (3.20171117.1) unstable; urgency=medium
.
* New upstream microcode data file 20171117
+ New Microcodes:
sig 0x000506c9, pf_mask 0x03, 2017-03-25, rev 0x002c, size 16384
sig 0x000706a1, pf_mask 0x01, 2017-10-31, rev 0x001e, size 72704
sig 0x000906ea, pf_mask 0x22, 2017-08-23, rev 0x0070, size 95232
sig 0x000906eb, pf_mask 0x02, 2017-09-20, rev 0x0072, size 97280
+ Updated Microcodes:
sig 0x00050654, pf_mask 0xb7, 2017-10-17, rev 0x2000035, size 26624
sig 0x000806ea, pf_mask 0xc0, 2017-08-03, rev 0x0070, size 96256
* source: remove superseded upstream data file: 20170707.
* source: remove unneeded intel-ucode/ directory for 20171117.
* debian/control: bump standards version to 4.1.1 (no changes)
* Makefile: rename microcode-extras.pbin to microcode-includes.pbin.
* README.source: fix IUC_EXCLUDE example and minor issues.
* Makefile, README.souce: support loading ucode from directories.
* debian/rules: switch to dh mode (debhelper v9)
* ucode-blacklist: blacklist sig 0x406f1 (Skylake-X H0) from late
loading.
.
intel-microcode (3.20170707.1~bpo9+1) stretch-backports; urgency=high
.
* Rebuild for stretch-backports (no changes)
.
intel-microcode (3.20170707.1) unstable; urgency=high
.
* New upstream microcode datafile 20170707
+ New Microcodes:
sig 0x00050654, pf_mask 0x97, 2017-06-01, rev 0x2000022, size 25600
sig 0x000806e9, pf_mask 0xc0, 2017-04-27, rev 0x0062, size 97280
sig 0x000806ea, pf_mask 0xc0, 2017-05-23, rev 0x0066, size 95232
sig 0x000906e9, pf_mask 0x2a, 2017-04-06, rev 0x005e, size 97280
+ This release fixes the nightmare-level errata SKZ7/SKW144/SKL150/
SKX150 (Skylake) KBL095/KBW095 (Kaby Lake) for all affected Kaby
Lake and Skylake processors: Skylake D0/R0 were fixed since the
previous upstream release (20170511). This new release adds the
fixes for Kaby Lake Y0/B0/H0 and Skylake H0 (Skylake-E/X).
+ Fix undisclosed errata in Skylake H0 (0x50654), Kaby Lake Y0
(0x806ea), Kaby Lake H0 (0x806e9), Kaby Lake B0 (0x906e9)
* source: remove unneeded intel-ucode/ directory
* source: remove superseded upstream data file: 20170511
.
intel-microcode (3.20170511.1) unstable; urgency=medium
.
* New upstream microcode datafile 20170511
+ Updated Microcodes:
sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb000021, size 26624
sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+ This release fixes undisclosed errata on the desktop, mobile and
server processor models from the Haswell, Broadwell, and Skylake
families, including even the high-end multi-socket server Xeons
+ Likely fix the TSC-Deadline LAPIC errata (BDF89, SKL142 and
similar) on several processor families
+ Fix erratum BDF90 on Xeon E7v4, E5v4(?) (closes: #862606)
+ Likely fix serious or critical Skylake errata: SKL138/144,
SKL137/145, SLK149
* Likely fix nightmare-level Skylake erratum SKL150. Fortunately,
either this erratum is very-low-hitting, or gcc/clang/icc/msvc
won't usually issue the affected opcode pattern and it ends up
being rare.
SKL150 - Short loops using both the AH/BH/CH/DH registers and
the corresponding wide register *may* result in unpredictable
system behavior. Requires both logical processors of the same
core (i.e. sibling hyperthreads) to be active to trigger, as
well as a "complex set of micro-architectural conditions"
* source: remove unneeded intel-ucode/ directory
Since release 20170511, upstream ships the microcodes both in .dat
format, and as Linux-style split /lib/firmware/intel-ucode files.
It is simpler to just use the .dat format file for now, so remove
the intel-ucode/ directory. Note: before removal, it was verified
that there were no discrepancies between the two microcode sets
(.dat and intel-ucode/)
* source: remove superseded upstream data file: 20161104
.
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
.
intel-microcode (3.20160714.1) unstable; urgency=medium
.
* New upstream microcode datafile 20160714
+ Updated Microcodes:
sig 0x000306f4, pf mask 0x80, 2016-06-07, rev 0x000d, size 15360
sig 0x000406e3, pf mask 0xc0, 2016-06-22, rev 0x009e, size 97280
sig 0x000406f1, pf mask 0xef, 2016-06-06, rev 0xb00001d, size 25600
sig 0x000506e3, pf mask 0x36, 2016-06-22, rev 0x009e, size 97280
+ This release hopefully fixes a hang when updating the microcode on
some Skylake-U D-1/Skylake-Y D-1 (sig 0x406e3, pf 0x80) systems
* source: remove superseded upstream data file: 20160607
.
intel-microcode (3.20160607.2) unstable; urgency=low
.
* REMOVE microcode:
sig 0x000406e3, pf mask 0xc0, 2016-04-06, rev 0x008a, size 96256
(closes: #828819)
* The Core i7-6500U and m3-6Y30 processors (Skylake-UY D-1,
sig=0x406e3, pf=0x80) may hang while attempting an early microcode
update to revision 0x8a, apparently due to some sort of firmware
dependency. On affected systems, the only way to avoid the issue is
to get a firmware update that includes microcode revision 0x8a or
later. At this time, there are reports of both sucessful and failed
updates on the m3-6Y30, and only of failed updates on the i7-6500U.
There are no reports about Skylake-U K-1 (pf=0x40).
+ WARNING: it is unsafe to use a system based on an Intel Skylake-U/Y
processor with microcode earlier than revision 0x8a, due to several
critical errata that cause unpredictable behavior, data corruption,
and other problems. Users *must* update their firmware to get
microcode 0x8a or newer, and keep it up-to-date.
.
intel-microcode (3.20160607.1) unstable; urgency=medium
.
* New upstream microcode data file 20160607
+ New Microcodes:
sig 0x000406e3, pf mask 0xc0, 2016-04-06, rev 0x008a, size 96256
sig 0x000406f1, pf mask 0xef, 2016-05-20, rev 0xb00001c, size 25600
sig 0x00050662, pf mask 0x10, 2015-12-12, rev 0x000f, size 28672
sig 0x000506e3, pf mask 0x36, 2016-04-06, rev 0x008a, size 96256
+ Updated Microcodes:
sig 0x000306c3, pf mask 0x32, 2016-03-16, rev 0x0020, size 22528
sig 0x000306d4, pf mask 0xc0, 2016-04-29, rev 0x0024, size 17408
sig 0x000306f2, pf mask 0x6f, 2016-03-28, rev 0x0038, size 32768
sig 0x000306f4, pf mask 0x80, 2016-02-11, rev 0x000a, size 15360
sig 0x00040651, pf mask 0x72, 2016-04-01, rev 0x001f, size 20480
sig 0x00040661, pf mask 0x32, 2016-04-01, rev 0x0016, size 24576
sig 0x00040671, pf mask 0x22, 2016-04-29, rev 0x0016, size 11264
* source: remove superseded upstream data file: 20151106.
* control: change upstream URL to a search for "linux microcode"
Unfortunately, many of the per-processor-model feeds have not been
updated for microcode release 20160607. Switch to the general search
page as the upstream URL.
* README.Debian: fix duplicated word 'to'
Checksums-Sha1:
baf1849a3f7512a662229856fe4ba39f71e68982 1825 intel-microcode_3.20171117.1~bpo9+1.dsc
3b6943d4f0245e9a0dfb59795749071428a9b1c1 1802168 intel-microcode_3.20171117.1~bpo9+1.tar.xz
5d7cc2a2fe425c6141db3f5c202b4fbf7d0fdc3e 5716 intel-microcode_3.20171117.1~bpo9+1_amd64.buildinfo
050e40e71e4ca08a20c5455076c336c00afbecdd 1269954 intel-microcode_3.20171117.1~bpo9+1_amd64.deb
8e6ba89e3179bb502a2bb1a2764ce267c0904aca 4496 intel-microcode_3.20171117.1~bpo9+1_i386.buildinfo
214fc852fa455bc264b2f94e235e2540be453fc5 1409248 intel-microcode_3.20171117.1~bpo9+1_i386.deb
Checksums-Sha256:
c9852bc3a72318809b4ca3580a9f199137d1139c8b5e81115e8cbdd5337cc24f 1825 intel-microcode_3.20171117.1~bpo9+1.dsc
d595dcb2bb8adfa992e67382597575dd713cfb782558d9541fdc589a8fe5bb2d 1802168 intel-microcode_3.20171117.1~bpo9+1.tar.xz
bdb90c7acc64b9b318a292b65d24079172dd04d4b599cc0f723f903456007972 5716 intel-microcode_3.20171117.1~bpo9+1_amd64.buildinfo
4fd7279aaa00c5186eb6ba37e21b92bfa0b0fdf1eece7d682391484451868946 1269954 intel-microcode_3.20171117.1~bpo9+1_amd64.deb
3257c6ffada447b5c8ad72544fb2dd671de8fb0e65715d6a7acb114b875296d6 4496 intel-microcode_3.20171117.1~bpo9+1_i386.buildinfo
97fe8d939807635b68ef70b702bd5b1363a9955475b8764ab114cf57262b956b 1409248 intel-microcode_3.20171117.1~bpo9+1_i386.deb
Files:
92e1e1ef9fd9f61e573380dd31df5d11 1825 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1.dsc
2496e379b4698d6040a47075cdcfe735 1802168 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1.tar.xz
f51048357cc83f417c4583496a4a4eae 5716 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1_amd64.buildinfo
fa9c3feb962f2e18bc9cd26f39c85ef0 1269954 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1_amd64.deb
d17e3856bd93f5601f7d78bf9bdf62b5 4496 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1_i386.buildinfo
10fb5f31596c90bf2d2efee538579d51 1409248 non-free/admin standard intel-microcode_3.20171117.1~bpo9+1_i386.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEq7GuO+cOOhDUp+2l/hG/posVjpgFAloa8iYACgkQ/hG/posV
jpjyLA//Sbn98ON13QXBKVPe6ZEPj2d23XYZuY8uxb1Z/XGQNmu6UMhLmCWzA4EU
0QNQD/1WZYID+Pe3IssdHG7Ta8ocv8B7/dPVHTOBKYvyNSAXrwILkQK0ZO/4YyuL
mMa4nLoiXdvgK/19mwmxbi4qIU8xG+9LiuRLP1SJoy36vdhrTYdeQ6+wt1KbAK9K
7MZBnM0qS6cLntNCIA3Ukvn7DwIshBySeNeUqsY+4KdjN5TZ8gReN1qCIeh9FgCQ
ZyIFMjWUHCDGLVoih/ViQ/S9HSGlWfq3eT4y2yWeNlx5RHVCRIaVCNHH0QAvsrHM
8gMW06JsimEY309EZAKEK7+snjsnQ7wARWb/mhA8HWuO3aOf7NeVrn+xDwOf2SLw
DTck+odrBAyncEMwPyfur5bqAGjnnuc3Mvzj8cSsWEF3qznfONrSU94zltvlT0Uv
awjTaCi7sGDRCJfaoUNzrOPg51mWF6yiwvyVxztbJtpeejhabjA5fB8cxQPDf8in
G97LKvqKIEhEdfVKvQq1VS2C7rA5+rh5ggfG+V1tw3NPg94HDrVNP22gFs6+f5tb
zdK/lTgmSqcahu40n0kds8pjvpAaFBd+sYOVZfSMC3d6nMhHxHYV0eI9TxF7eHTD
Mw7bQ3VnVJXiyBpnGoeYvizEq8Jck5Ux6h8VY4b/qdJc3f2ZIUU=
=atfp
-----END PGP SIGNATURE-----
Reply to: