1 |
On Tue, 09 Jan 2018 14:21:10 +0000, Holger Hoffstätte wrote: |
2 |
|
3 |
> On Mon, 08 Jan 2018 11:53:58 +0000, Mick wrote: |
4 |
> |
5 |
>> On Monday, 8 January 2018 09:05:02 GMT Max Zettlmeißl wrote: |
6 |
>>> It seems like there are no microcode updates for your specific CPU |
7 |
>>> bundled in linux-firmware. |
8 |
>> |
9 |
>> Only two out of three Intel boxen here report an early update of microcode in |
10 |
>> dmesg. Even when they do, it is not certain the latest firmware has brought |
11 |
>> new code: |
12 |
>> |
13 |
>> [ 0.000000] microcode: microcode updated early to revision 0x7, date = |
14 |
>> 2013-08-20 |
15 |
>> |
16 |
>> This date above puzzles me. Is it that on this PC's CPU the Intel bugs cannot |
17 |
>> be ameliorated by the latest intel-ucode release, or is it that Intel have not |
18 |
>> bothered to release microcode revisions for all their products. |
19 |
> |
20 |
> The latter - older CPUs simply don't get updates. My server & workstation |
21 |
> are i5/i7 SandyBridge built in early 2012, and their last microcode updates |
22 |
> are from 2013 as well. |
23 |
> |
24 |
>> Therefore if microcode for my CPU was included in intel-ucode releases since |
25 |
>> 2017-01-01, is this the same unchanged microcode being released since the date |
26 |
>> reported in dmesg of 2013-08-20? |
27 |
> |
28 |
> Seems like it. |
29 |
|
30 |
Just read that Intel plans to ship microcode updates for CPUs built in and |
31 |
after *2013*, so I guess that means anything after & including Ivy Bridge. |
32 |
|
33 |
Announcement: https://www.youtube.com/watch?v=RlJ9zB74G_U |
34 |
|
35 |
All my machines will be running AMD very soon. I need more cores anyway. |
36 |
|
37 |
-h |