public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] microcode applied?
Date: Mon, 08 Jan 2018 11:53:58 +0000	[thread overview]
Message-ID: <3425468.ZtkkVYOytn@dell_xps> (raw)
In-Reply-To: <CACjvM=fuyZZwtoz_Cv6VnS8p_ktjrO8t45+iRMaWvv00uuNDzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

On Monday, 8 January 2018 09:05:02 GMT Max Zettlmeißl wrote:
> It seems like there are no microcode updates for your specific CPU
> bundled in linux-firmware.

Only two out of three Intel boxen here report an early update of microcode in 
dmesg.  Even when they do, it is not certain the latest firmware has brought 
new code:

[    0.000000] microcode: microcode updated early to revision 0x7, date = 
2013-08-20

This date above puzzles me.  Is it that on this PC's CPU the Intel bugs cannot 
be ameliorated by the latest intel-ucode release, or is it that Intel have not 
bothered to release microcode revisions for all their products.

Running in the directory /lib/firmware/intel-ucode the following command:

iucode_tool -v --date-after=2017-01-01  --write-all-named-to=TEST .

spews out into TEST/ the microcode for this CPU:

s000106E5_m00000013_r00000007.fw

Therefore if microcode for my CPU was included in intel-ucode releases since 
2017-01-01, is this the same unchanged microcode being released since the date 
reported in dmesg of 2013-08-20?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-09  1:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  3:24 [gentoo-user] microcode applied? Adam Carter
2018-01-08  4:01 ` Max Zettlmeißl
2018-01-08  4:23   ` Adam Carter
2018-01-08  4:55     ` Max Zettlmeißl
2018-01-08  5:41       ` Adam Carter
2018-01-08  9:05         ` Max Zettlmeißl
2018-01-08 11:53           ` Mick [this message]
2018-01-09 14:21             ` [gentoo-user] " Holger Hoffstätte
2018-01-09 14:31               ` Holger Hoffstätte
2018-01-08 10:14       ` [gentoo-user] " Peter Humphrey
2018-01-08 10:29         ` Max Zettlmeißl
2018-01-09  0:15           ` Peter Humphrey
2018-01-09  7:31             ` Mick
2018-01-09  9:33               ` Peter Humphrey
2018-01-09  8:43             ` Neil Bothwick
2018-01-09  8:56             ` Adam Carter
2018-01-09  9:58               ` Adam Carter
2018-01-09  9:02             ` Jorge Almeida
2018-01-08 21:22         ` Adam Carter
2018-01-08  4:42   ` mad.scientist.at.large
2018-01-08 13:52     ` Rich Freeman
2018-01-09  9:26       ` Wols Lists
2018-01-09 13:35         ` Rich Freeman
2018-01-08 17:55 ` Corbin Bird

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3425468.ZtkkVYOytn@dell_xps \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox