From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-181971-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 7A7CD138330
	for <garchives@archives.gentoo.org>; Thu, 11 Jan 2018 05:08:11 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id BBEA2E0C02;
	Thu, 11 Jan 2018 05:08:03 +0000 (UTC)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 532D8E0B9E
	for <gentoo-user@lists.gentoo.org>; Thu, 11 Jan 2018 05:08:03 +0000 (UTC)
Received: by mail-oi0-x229.google.com with SMTP id o64so880898oia.9
        for <gentoo-user@lists.gentoo.org>; Wed, 10 Jan 2018 21:08:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=rRHClk+Ge63HSEBMqwiWZIMIgUoIpou3xVij5A9aEFU=;
        b=svZx9Z/pTgSgFS+PLe7s1C1ZEg0Bv6YnqTghUKlEQzuIi2Avg2+0WX/110J6/5mqiM
         3I5n5iDj9R0itS61GmycYPg5o18mc1LfTzwBIpgS3c35/u173RZ63QKPP9u6CLOjcAIJ
         +6t7MQZZHViXpUVigHbCa/iyi0fwDeKo/Ay2/8+T5zta5mo30jABndtkk/PB4JaN8lN4
         f7nlJwYAkwTaq42LJTTzoETsEdXRLy2IbasKh22GVBYcEDrcvcgUTssDGuvIhNBUJMbl
         L3P4Gg0hMMVbYfU2jclj1aVBX/+dyGQc+ug/pMmBhz+HLDo8nMAtxVGs/oDDPeSMMB4p
         bsjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=rRHClk+Ge63HSEBMqwiWZIMIgUoIpou3xVij5A9aEFU=;
        b=eTZFj52DlnGxUCO1Jy4PB9brJvXfvC76JcuENTUl9aCUz7UhDFgAz07CKeXF/HuVMt
         jp4xLea22/qFAd3KEeRSLhLzosIG9uj6KPr/M2wMe0A+JCX5zO6zlSfhk3q+ONGk7+xI
         rMqUUviCcO8QYxtC+JUCRxmmRQyr8S/oFQDNIKf55qrxFrKZvPDBkicCoJZKtNu/zF3X
         mAAxPI1mRxAxRImcoyTLfqMPuXCPHAUroCvKrgt+HhhdO02iRkjA1J1XlddsZJW0Mswc
         Oylb6tbr37OFXpFuUojCh83vNptSHChgGLfF4+5wjrkXYFm7qfc8yB6q5XZx6EDCr5n3
         pD0g==
X-Gm-Message-State: AKwxytftbMuFo5eLFmLhCRPrtPBlQN+Kke1IwRiKR3dYxp5pUIqW4zYY
	EVuupr28rYWBZoM53G4YwDLQwx14ViLz1fLd+dLXOkJ9
X-Google-Smtp-Source: ACJfBotCsXrgnz5MjpAsKYM+x+3hZ97f3P/QA4tkxXogcoalk9a/gqi4jx6DvzNMHuocObZyzgkiU7DWa1DtSo5xOCk=
X-Received: by 10.202.117.4 with SMTP id q4mr279985oic.34.1515647282147; Wed,
 10 Jan 2018 21:08:02 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.157.19.65 with HTTP; Wed, 10 Jan 2018 21:08:01 -0800 (PST)
In-Reply-To: <CAC=wYCFHJ1gK-+PhtBAP9wtTKMd_SKbq+sXMix0Xsg9stVTq9Q@mail.gmail.com>
References: <2128113.qSj3GTADmc@peak> <CAC=wYCFHJ1gK-+PhtBAP9wtTKMd_SKbq+sXMix0Xsg9stVTq9Q@mail.gmail.com>
From: Adam Carter <adamcarter3@gmail.com>
Date: Thu, 11 Jan 2018 16:08:01 +1100
Message-ID: <CAC=wYCHcAC69xCivGQWPQYGEDCg9iLJoz3-CGf8LQUbvmHusZg@mail.gmail.com>
Subject: Re: [gentoo-user] Is sys-firmware/intel-microcode-20180108 complete?
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary="001a1137be76db7b2a0562792178"
X-Archives-Salt: d0e6a081-bda6-4b41-bf1d-e8ce1a46d3af
X-Archives-Hash: 1571c95f9f0f14f8153d8165620e7f36

--001a1137be76db7b2a0562792178
Content-Type: text/plain; charset="UTF-8"

> It looks as though my CPU hasn't been fixed yet. Is that right?
>>
>
> That's odd - i wonder why the checksum of the file changed;
>
> # grep 06-3f-02 intel-firmware-md5s-9jan2018.txt
> intel-firmware-md5s-10jan2018.txt
> intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749
> /lib/firmware/intel-ucode/06-3f-02
> intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93
> /lib/firmware/intel-ucode/06-3f-02
>
>
And with intel-microcode-20180108-r1 its back to what it was;

# grep 06-3f-02 intel-firmware-md5s-9jan2018.txt
intel-firmware-md5s-10jan2018.txt intel-firmware-md5s-11jan2018.txt
intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749
/lib/firmware/intel-ucode/06-3f-02
intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93
/lib/firmware/intel-ucode/06-3f-02
intel-firmware-md5s-11jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749
/lib/firmware/intel-ucode/06-3f-02

Looks like there was an issue with intel-microcode-20180108.

50/94 files are different from intel-microcode-20171117_p20171215-r1 to
intel-microcode-20180108-r1, they are;
06-05-00
06-05-02
06-05-03
06-06-0a
06-06-0d
06-08-01
06-08-03
06-08-06
06-08-0a
06-09-05
06-0b-01
06-0b-04
06-0e-0c
06-0f-02
06-0f-06
06-0f-07
06-0f-0b
06-0f-0d
06-16-01
06-17-06
06-17-0a
06-1c-02
06-1c-0a
06-26-01
06-3e-04
06-3f-04
06-46-01
06-47-01
06-4f-01
06-55-04
06-56-02
06-56-03
06-5c-09
06-5e-03
06-7a-01
06-8e-09
06-8e-0a
06-9e-09
06-9e-0a
06-9e-0b
0f-00-07
0f-00-0a
0f-02-04
0f-02-05
0f-02-07
0f-02-09
0f-04-01
0f-04-08
0f-04-0a
0f-06-04

--001a1137be76db7b2a0562792178
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><span cl=
ass=3D"gmail-"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">
It looks as though my CPU hasn&#39;t been fixed yet. Is that right?<br></bl=
ockquote></div></div><div class=3D"gmail_extra"><br></div></span><div class=
=3D"gmail_extra">That&#39;s odd - i wonder why the checksum of the file cha=
nged;</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">=
# grep 06-3f-02 intel-firmware-md5s-9jan2018.<wbr>txt intel-firmware-md5s-1=
0jan2018.<wbr>txt <br>intel-firmware-md5s-9jan2018.<wbr>txt:<wbr>194c362f2c=
45d8a45e2ab58d5f2c97<wbr>49=C2=A0 /lib/firmware/intel-ucode/06-<wbr>3f-02<b=
r>intel-firmware-md5s-10jan2018.<wbr>txt:<wbr>b6e684762e7212054271c9441048f=
a<wbr>93=C2=A0 /lib/firmware/intel-ucode/06-<wbr>3f-02<br><br></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">And with intel-micr=
ocode-20180108-r1 its back to what it was;</div><div class=3D"gmail_extra">=
<br></div><div class=3D"gmail_extra"># grep 06-3f-02 intel-firmware-md5s-9j=
an2018.txt intel-firmware-md5s-10jan2018.txt intel-firmware-md5s-11jan2018.=
txt <br>intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749=
=C2=A0 /lib/firmware/intel-ucode/06-3f-02<br>intel-firmware-md5s-10jan2018.=
txt:b6e684762e7212054271c9441048fa93=C2=A0 /lib/firmware/intel-ucode/06-3f-=
02<br>intel-firmware-md5s-11jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749=C2=
=A0 /lib/firmware/intel-ucode/06-3f-02<br></div><div class=3D"gmail_extra">=
<br></div><div class=3D"gmail_extra">Looks like there was an issue with int=
el-microcode-20180108.</div><div class=3D"gmail_extra"></div><div class=3D"=
gmail_extra"><br></div><div class=3D"gmail_extra">50/94 files are different=
 from intel-microcode-20171117_p20171215-r1 to intel-microcode-20180108-r1,=
 they are;<br></div><div class=3D"gmail_extra">06-05-00<br>06-05-02<br>06-0=
5-03<br>06-06-0a<br>06-06-0d<br>06-08-01<br>06-08-03<br>06-08-06<br>06-08-0=
a<br>06-09-05<br>06-0b-01<br>06-0b-04<br>06-0e-0c<br>06-0f-02<br>06-0f-06<b=
r>06-0f-07<br>06-0f-0b<br>06-0f-0d<br>06-16-01<br>06-17-06<br>06-17-0a<br>0=
6-1c-02<br>06-1c-0a<br>06-26-01<br>06-3e-04<br>06-3f-04<br>06-46-01<br>06-4=
7-01<br>06-4f-01<br>06-55-04<br>06-56-02<br>06-56-03<br>06-5c-09<br>06-5e-0=
3<br>06-7a-01<br>06-8e-09<br>06-8e-0a<br>06-9e-09<br>06-9e-0a<br>06-9e-0b<b=
r>0f-00-07<br>0f-00-0a<br>0f-02-04<br>0f-02-05<br>0f-02-07<br>0f-02-09<br>0=
f-04-01<br>0f-04-08<br>0f-04-0a<br>0f-06-04<br></div></div>

--001a1137be76db7b2a0562792178--