Accepted intel-microcode 3.20160714.1~deb8u1~bpo7+1 (amd64 i386 source) into wheezy-backports->backports-policy, wheezy-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 24 Sep 2016 09:03:03 -0300
Source: intel-microcode
Binary: intel-microcode
Architecture: amd64 i386 source
Version: 3.20160714.1~deb8u1~bpo7+1
Distribution: wheezy-backports
Urgency: medium
Maintainer: Henrique de Moraes Holschuh <hmh@debian.org>
Changed-By: Henrique de Moraes Holschuh <hmh@debian.org>
Closes: 814301 828819
Description:
intel-microcode - Processor microcode firmware for Intel CPUs
Changes:
intel-microcode (3.20160714.1~deb8u1~bpo7+1) wheezy-backports; urgency=medium
.
* Rebuild for Debian wheezy-backports (no changes)
This is the same package as 3.20160714.1~deb8u1
.
intel-microcode (3.20160714.1~deb8u1) stable; urgency=medium
.
* Rebuild for Debian jessie stable update (no changes)
* STABLE RELEASE MANAGER INFORMATION:
+ This is the same package which is in unstable since 2016-07-22,
and stretch (testing) and jessie-backports since 2016-07-28,
with no issues reported
+ Contains updated microcode for:
Skylake/H/DT, Broadwell/E/EP/H/DE/WS, Haswell/E/WS/EP/EX, and their
usual variants (U/ULT,Y,S...): mobile, desktop, embedded, single-
and dual-socket server/workstation. Also includes related Pentium
and Celeron
+ Somewhat unusually, this release includes an update for the
multi-socket Haswell-EX E7-v3 Xeon server processors
+ Fixes critical issues on Intel Skylake processors, such as:
- TSX unpredictable behavior
- AVX data/calculation corruption
- High-hitting crashes and hangs related to MCEs and power
management errata that might make it impossible to even install
Debian in the first place (systems with very outdated firmware)
+ Likely fixes a recently identified, critical but low-hitting TSX
erratum on Broadwell, Broadwell-E and related Xeons
(Broadwell-DE/WS/EP: Xeon-D 1500, E3-v4 and E5-v4)
+ Fix Broadwell-DE (Xeon-D 1500) errata (incomplete list):
Stepping V-1: BDE58, BDE56, BDE55, BDE50, BDE44, BDE41, BDE38,
BDE10, BDE9, BDE8, BDE7
Stepping Y-0: LAN1, BDE67, BDE68
+ Might fix Haswell-EP Xeon E5-v3 power management regression
which is already present in the packages currently in jessie
(#815990)
+ Fixes undisclosed errata on Xeon E7-v3 48xx/88xx
.
intel-microcode (3.20160714.1~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports (no changes)
.
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~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports (no changes)
.
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~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports (no changes)
.
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'
.
intel-microcode (3.20151106.2) unstable; urgency=medium
.
* Makefile: make the build less verbose.
* debian/changelog: fix error in past entry.
Correct the version of the microcode that caused bug #776431,
in the entry for version 3.20150121.1.
* initramfs: don't force_load microcode.ko when missing.
Detect a missing microcode.ko and don't attempt to force_load() it,
otherwise we get spurious warnings at boot. In verbose mode, log the
fact that the microcode driver is modular. For Linux 4.4 and later,
skip the entire module loading logic, since the microcode driver cannot
be modular for those kernels (closes: #814301).
* initramfs: update copyright notice
* initramfs: use iucode_tool -l for verbose mode
* README.Debian: enhance and add recovery instructions.
Rewrite large parts of the README.Debian document, and add recovery
instructions (use of the "dis_ucode_ldr" kernel parameter).
.
intel-microcode (3.20151106.1~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports (no changes)
Checksums-Sha1:
a5986328e666fc324a8109de8060ac5233f1f547 1823 intel-microcode_3.20160714.1~deb8u1~bpo7+1.dsc
872b611caede9dc84937fde422d7c03c578d7358 1137372 intel-microcode_3.20160714.1~deb8u1~bpo7+1.tar.xz
fb2d14eb2bac12b867a6bf615823c75c7f3eb831 734096 intel-microcode_3.20160714.1~deb8u1~bpo7+1_amd64.deb
ba71e74aa8433b215eef5d15615ba4fd0374c101 877344 intel-microcode_3.20160714.1~deb8u1~bpo7+1_i386.deb
Checksums-Sha256:
e9ec38724ab8f9e8e9f01c6a143c7001cfd759b6a556c60ec15249636e3640e3 1823 intel-microcode_3.20160714.1~deb8u1~bpo7+1.dsc
a457affab983399b66cd073cbb99eac492112a5d5533891e13ee8469d3e6b3e2 1137372 intel-microcode_3.20160714.1~deb8u1~bpo7+1.tar.xz
8076075880ba6714a6611a10cd77fa59a1546cff55c95b8d163cd3b7f01bd711 734096 intel-microcode_3.20160714.1~deb8u1~bpo7+1_amd64.deb
bc6ff47aa703603571c3786c0e3c3729d24b244aa62627bed6fb5ec99924a946 877344 intel-microcode_3.20160714.1~deb8u1~bpo7+1_i386.deb
Files:
06cb48fe5dfd59ea44a2ad1c6031febc 1823 non-free/admin standard intel-microcode_3.20160714.1~deb8u1~bpo7+1.dsc
72eec5fdd2301ffecd31f15368b8bdc6 1137372 non-free/admin standard intel-microcode_3.20160714.1~deb8u1~bpo7+1.tar.xz
ad4ae805628f6ce0a5f579d953b3bc29 734096 non-free/admin standard intel-microcode_3.20160714.1~deb8u1~bpo7+1_amd64.deb
c8414441a9803d5ede440a96e6e93bfd 877344 non-free/admin standard intel-microcode_3.20160714.1~deb8u1~bpo7+1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJX5m3jAAoJEP4Rv6aLFY6YKmkP/3tXRLmWvehZmFSjIHybGH8s
H1O6JaMl9/V67p7kA9SSlVUprxaO5JJpGs8nkKLF1F8Cd17mpo/pNcgY6hvO6r7A
TrBIoRMkQuPcfinWj7S2rhzr+I0pk21mWgEejS6IuMP9E13JFh4vx0+f869m/vuN
LdVjtAgQh6TZGYbtVHe5mt1yFW4Mdz8mKpZ5aD4GOPDOyMVYg/565mQyKsIMF2ic
7fLDjj4ovcKaa7ng3OfV/ekR368m+5YWPzJXFgg4nMT11VzOLHjMb0exNrGr0P16
sYr9F6KQ+fPfT6Z9GoEjAe1S7y2jBmqVCJyR16MjwN+tnqX0NEk/TSgcO6qH7sgp
PCzIxvl/sk5JgB3Gf5FzXczGLjViWM686XdkjoYUUAQEiVQN0SV/8V60FiYiliFm
QymAORMfJnIiMvWWP6y6XJ/qVpsrTg2Nm/r/tzq3keHPt+sRqjnToKjLucBgLxOZ
Wob6SFmecvYvtRxdQ9608y74vTIvZS1tb9JAV3pK27Ssji6qUf4Cu2UAQb9J+11z
Y92eviIcLu8+1bzg4Zq60czu9m/t4nhxKYJX4C394OxQjPjT7nf0bTogLLGvGaMq
ZOPSt5ssPsaI300aamQ4uHopMUYlC0bM/JDC22y4cV7/41bZemOgvZXY04DdDKJw
uBPVfz35asD+cW8la8vI
=VYnS
-----END PGP SIGNATURE-----
Reply to: