From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 27C1E138330 for ; Tue, 9 Jan 2018 14:33:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 26915E0B01; Tue, 9 Jan 2018 14:33:21 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (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 97390E0AF7 for ; Tue, 9 Jan 2018 14:33:20 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eYuvq-00081m-V4 for gentoo-user@lists.gentoo.org; Tue, 09 Jan 2018 15:31:14 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Holger =?iso-8859-1?q?Hoffst=E4tte?= Subject: [gentoo-user] Re: microcode applied? Date: Tue, 9 Jan 2018 14:31:00 +0000 (UTC) Message-ID: References: <3425468.ZtkkVYOytn@dell_xps> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Pan/0.142 (He slipped to Sam a double gin; 01b5bf4 git.gnome.org/pan2) X-Archives-Salt: f8970d4a-f2a0-42d0-832c-5bcfe198a45b X-Archives-Hash: 44a8a895b04020a2c57c75844dee9787 On Tue, 09 Jan 2018 14:21:10 +0000, Holger Hoffstätte wrote: > On Mon, 08 Jan 2018 11:53:58 +0000, Mick wrote: > >> 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. > > The latter - older CPUs simply don't get updates. My server & workstation > are i5/i7 SandyBridge built in early 2012, and their last microcode updates > are from 2013 as well. > >> 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? > > Seems like it. Just read that Intel plans to ship microcode updates for CPUs built in and after *2013*, so I guess that means anything after & including Ivy Bridge. Announcement: https://www.youtube.com/watch?v=RlJ9zB74G_U All my machines will be running AMD very soon. I need more cores anyway. -h