[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted intel-microcode 3.20161104.1~deb8u1~bpo7+1 (amd64 i386 source) into wheezy-backports->backports-policy, wheezy-backports



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 12:10:48 -0200
Source: intel-microcode
Binary: intel-microcode
Architecture: amd64 i386 source
Version: 3.20161104.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>
Description: 
 intel-microcode - Processor microcode firmware for Intel CPUs
Changes: 
 intel-microcode (3.20161104.1~deb8u1~bpo7+1) wheezy-backports; urgency=medium
 .
   * Rebuild for Debian wheezy-backports (no changes)
     This is the same package as 3.20161104.1~deb8u1
 .
 intel-microcode (3.20161104.1~deb8u1) stable; urgency=medium
 .
   * This is the same package as 3.20161104.1 from unstable/testing and
     3.20161104.1~bpo8+1, from jessie-backports.  It has been present in
     unstable since 2016-11-09, testing since 2016-11-15, and jessie-backports
     since 2016-11-17.
   * STABLE RELEASE MANAGER INFORMATION:
     + Supposed to fix critical Intel TSX erratum BDE85 on Xeon-D 1500 Y0
     + Known to fix critical errata on several Xeon-D 1500 models which
       will crash vmware (KB2146388) and likely Linux as well
     + Fixes likely critical errata (which ones unknown) on Broadwell-E
       (Core extreme edition 5th gen, Xeon E5v4, Xeon E7v4)
     + Removes (very likely outdated) microcode for the C3500 and C5500 family
       of embedded Xeon (Jasper Forest).  These embedded Xeons are typically
       found on (older) network equipment appliances such as firewalls/IPS/IDS,
       and also on data storage devices, and thus are supposed to receive
       microcode updates through their vendors
 .
 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: 
 6682febdf06107914f105ea99487b83a76a790b4 1823 intel-microcode_3.20161104.1~deb8u1~bpo7+1.dsc
 d114b724f96d432b04c7e73b01d185bb7c0de569 1187544 intel-microcode_3.20161104.1~deb8u1~bpo7+1.tar.xz
 9b530f60047de6f6d4e3b3f00810f4fdf9fc25d9 770714 intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd64.deb
 8b79b84103863d1ef67c521362a698692bd1483f 913664 intel-microcode_3.20161104.1~deb8u1~bpo7+1_i386.deb
Checksums-Sha256: 
 00d059b6d0846952686c819d8534febe5aaa4e5ffec521e1dac06def6b78c34c 1823 intel-microcode_3.20161104.1~deb8u1~bpo7+1.dsc
 ba9a96f58e5d2aff8ca360668131137d8ae620ba563538866b76effb9317cd89 1187544 intel-microcode_3.20161104.1~deb8u1~bpo7+1.tar.xz
 e68f13f3321cdf33f360d7bf77bc1c995abf85d29b07b030fad1f929b92a25f1 770714 intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd64.deb
 6646bf2f0279080b35829245f029aa8e9c70f3570876e4adfccfabc1ca3b849e 913664 intel-microcode_3.20161104.1~deb8u1~bpo7+1_i386.deb
Files: 
 2f1298fd4dd0bb447704373eb8191afe 1823 non-free/admin standard intel-microcode_3.20161104.1~deb8u1~bpo7+1.dsc
 72497a69f1567a56c83d7b97c598b543 1187544 non-free/admin standard intel-microcode_3.20161104.1~deb8u1~bpo7+1.tar.xz
 7f802e64e53eb5c79458e4801390b260 770714 non-free/admin standard intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd64.deb
 14c6b73945d1b8fc19a4b17e7590b720 913664 non-free/admin standard intel-microcode_3.20161104.1~deb8u1~bpo7+1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJYe5K6AAoJEP4Rv6aLFY6Y0TkP/iPovz3IsV36WNXOTbXtkUBw
vsx8PJcZbnzKd5e1tujDr6nvZjP352TPucGBcbt+G14FmbVVHY1oJcTTVEMP988s
KRCjqki/3LW2fDFNvbXQQH/JjxsIF4b/6uXWgqmY6InNadpkQcVsSA1bmD2302mS
s8ftajDNHjdleDOfKRNov30PXbVrv1LAaI8vjZZh7UeiTtSrgD6Mly4flbAPkdza
V1tHgD0CPiO+IoesM7+vcs8jOXYbjbVMjhxSUnVYjgqQ7T2jQzZEDh62MdI85VcY
F7sggXYNnA10mW934k3fv6XOHpQGSNBSorpAgWVVLld/TAnQBM8QfMvBEbymhO4u
pObZcTNR6CLE8kdr9oACyd5A0sF2nF+44sBDnJD7jaj30glEMpFlKauydASconu6
wnXqhkG6mWuEUGUb67HP19W1LZryV+ofWWneoytnlrauO8yv1cscyrUglSs2wwb9
9UW4bo3U73Yj49DYp1sM6KcUqxtJpXaT0XvrsoD0Fsale8gem6D2MjAZZPoEKsDG
FU5NntGlRL+6o90ss9vpLyuv5KM1swvk/7AYAOM9bBrTGsbk3xVhPNq7+SZfeCSX
zUJ0706VAxPInrIBWYe036+g3ja7jo6XmUfDm46w08J+qLLXpIuHV1m7MZswtyhK
81V/ES7wg4DKn/N5yabT
=SIUs
-----END PGP SIGNATURE-----


Reply to: