[arch-general] Intel microcode - latest version not loading
Hi all: I'm having an issue with Intel microcode loading. Specifically, the microcode does not appear to be loading the latest version: ~ $ dmesg | grep microcode [ 0.000000] microcode: microcode updated early to revision 0x19, date = 2013-06-21 [ 0.931272] microcode: sig=0x106a5, pf=0x2, revision=0x19 [ 0.931319] microcode: Microcode Update Driver: v2.2. My processor is: ~ $ grep -E 'family|model|stepping' -m 4 /proc/cpuinfo cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3503 @ 2.40GHz stepping : 5 The Intel website indicates the latest version of microcode for this processor is version 20171117 [1]. However, as indicated above, the version loaded at boot is dated 2013-06-21. I have the latest stable version of intel-ucode installed: ~ $ pacman -Q intel-ucode intel-ucode 20180108-1 I have updated GRUB with <grub-mkconfig -o /boot/grub/grub.cfg>, and rebooted. The grub.cfg file shows, as the last line in the menuentry: 'initrd /boot/intel-ucode.img /boot/initramfs-linux.img' I am using a stock kernel: ~ $ uname -a Linux arch2 4.15.5-1-ARCH #1 SMP PREEMPT Thu Feb 22 22:15:20 UTC 2018 x86_64 GNU/Linux Can someone help me determine what is going on here? [1] https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Da...
On Wed, 28 Feb 2018 11:46:23 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
Hi all:
I'm having an issue with Intel microcode loading. Specifically, the microcode does not appear to be loading the latest version:
~ $ dmesg | grep microcode [ 0.000000] microcode: microcode updated early to revision 0x19, date = 2013-06-21 [ 0.931272] microcode: sig=0x106a5, pf=0x2, revision=0x19 [ 0.931319] microcode: Microcode Update Driver: v2.2.
My processor is:
~ $ grep -E 'family|model|stepping' -m 4 /proc/cpuinfo cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3503 @ 2.40GHz stepping : 5
The Intel website indicates the latest version of microcode for this processor is version 20171117 [1]. However, as indicated above, the version loaded at boot is dated 2013-06-21.
I have the latest stable version of intel-ucode installed:
~ $ pacman -Q intel-ucode intel-ucode 20180108-1
I have updated GRUB with <grub-mkconfig -o /boot/grub/grub.cfg>, and rebooted. The grub.cfg file shows, as the last line in the menuentry: 'initrd /boot/intel-ucode.img /boot/initramfs-linux.img'
I am using a stock kernel:
~ $ uname -a Linux arch2 4.15.5-1-ARCH #1 SMP PREEMPT Thu Feb 22 22:15:20 UTC 2018 x86_64 GNU/Linux
Can someone help me determine what is going on here?
[1] https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Da...
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine. Scimmia
On Wed, 28 Feb 2018 11:50:09 -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor.
Let alone that the µcode could be fishy, as it seemingly is for my CPU. I don't expect that Intel will support older CPUs. [rocketmouse@archlinux ~]$ hwinfo --cpu | grep Model | sort -u Model: 6.60.3 "Intel(R) Celeron(R) CPU G1840 @ 2.80GHz" [rocketmouse@archlinux ~]$ dmesg | grep microcode [ 0.000000] microcode: microcode updated early to revision 0x23, date = 2017-11-20 [ 0.000000] Intel Spectre v2 broken microcode detected; disabling Speculation Control [ 0.329718] microcode: sig=0x306c3, pf=0x2, revision=0x23 [ 0.329837] microcode: Microcode Update Driver: v2.2. [rocketmouse@archlinux ~]$ ls -hAl /sys/devices/system/cpu/vulnerabilities/ total 0 -r--r--r-- 1 root root 4.0K Feb 28 04:11 meltdown -r--r--r-- 1 root root 4.0K Feb 28 04:11 spectre_v1 -r--r--r-- 1 root root 4.0K Feb 28 04:11 spectre_v2 [rocketmouse@archlinux ~]$ cat /sys/devices/system/cpu/vulnerabilities/* Mitigation: PTI Mitigation: __user pointer sanitization Mitigation: Full generic retpoline -- $ pacman -Q linux{,-rt-securityink,-rt,-rt-pussytoes,-rt-cornflower} linux 4.15.6-1 linux-rt-securityink 4.14.20_rt17-1 linux-rt 4.14.12_rt10-1 linux-rt-pussytoes 4.14.8_rt9-2 linux-rt-cornflower 4.11.12_rt16-1
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
On Wed, 28 Feb 2018 11:46:23 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
Hi all:
I'm having an issue with Intel microcode loading. Specifically, the microcode does not appear to be loading the latest version:
~ $ dmesg | grep microcode [ 0.000000] microcode: microcode updated early to revision 0x19, date = 2013-06-21 [ 0.931272] microcode: sig=0x106a5, pf=0x2, revision=0x19 [ 0.931319] microcode: Microcode Update Driver: v2.2.
My processor is:
~ $ grep -E 'family|model|stepping' -m 4 /proc/cpuinfo cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3503 @ 2.40GHz stepping : 5
The Intel website indicates the latest version of microcode for this processor is version 20171117 [1]. However, as indicated above, the version loaded at boot is dated 2013-06-21.
I have the latest stable version of intel-ucode installed:
~ $ pacman -Q intel-ucode intel-ucode 20180108-1
I have updated GRUB with <grub-mkconfig -o /boot/grub/grub.cfg>, and rebooted. The grub.cfg file shows, as the last line in the menuentry: 'initrd /boot/intel-ucode.img /boot/initramfs-linux.img'
I am using a stock kernel:
~ $ uname -a Linux arch2 4.15.5-1-ARCH #1 SMP PREEMPT Thu Feb 22 22:15:20 UTC 2018 x86_64 GNU/Linux
Can someone help me determine what is going on here?
[1] https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Da...
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia
Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img?
On Wed, 28 Feb 2018 12:43:26 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia
Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img?
The img file can be extracted with bsdtar. iucode_tool in the AUR used for working with the intel bin file inside of that .img file. It can list, extract, search, and more. There's even an example on the Microcode wiki page.
On Wed, Feb 28, 2018 at 04:54:03PM -0600, Doug Newgard via arch-general wrote:
On Wed, 28 Feb 2018 12:43:26 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia
Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img?
The img file can be extracted with bsdtar. iucode_tool in the AUR used for working with the intel bin file inside of that .img file. It can list, extract, search, and more. There's even an example on the Microcode wiki page.
Did you just add that wiki page information?? (I'm just kidding, of course.) Totally missed it - thanks for the info!
Am 01.03.2018 um 00:41 schrieb Dutch Ingraham:
On Wed, Feb 28, 2018 at 04:54:03PM -0600, Doug Newgard via arch-general wrote:
On Wed, 28 Feb 2018 12:43:26 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img? The img file can be extracted with bsdtar. iucode_tool in the AUR used for working with the intel bin file inside of that .img file. It can list, extract, search, and more. There's even an example on the Microcode wiki page.
Did you just add that wiki page information?? (I'm just kidding, of course.) Totally missed it - thanks for the info!
In February Intel also released a PDF with available and planned microcode updates. The original now asks for a login, but this is a mirror: http://www-pc.uni-regensburg.de/systemsw/security/microcode-update-guidance_... Original location: https://newsroom.intel.com/wp-content/uploads/sites/11/2018/02/microcode-upd...
On Thu, Mar 01, 2018 at 08:13:08PM +0100, ProgAndy wrote:
Am 01.03.2018 um 00:41 schrieb Dutch Ingraham:
On Wed, Feb 28, 2018 at 04:54:03PM -0600, Doug Newgard via arch-general wrote:
On Wed, 28 Feb 2018 12:43:26 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img? The img file can be extracted with bsdtar. iucode_tool in the AUR used for working with the intel bin file inside of that .img file. It can list, extract, search, and more. There's even an example on the Microcode wiki page.
Did you just add that wiki page information?? (I'm just kidding, of course.) Totally missed it - thanks for the info!
In February Intel also released a PDF with available and planned microcode updates. The original now asks for a login, but this is a mirror:
http://www-pc.uni-regensburg.de/systemsw/security/microcode-update-guidance_...
Original location: https://newsroom.intel.com/wp-content/uploads/sites/11/2018/02/microcode-upd...
That's excellent information. Apparently, my 8 year old Core2 may soon be getting its first MCU!
There is a newer version of that file dated February 26th but I can't remember where I downloaded it from. On Thu, Mar 1, 2018 at 7:59 PM, Dutch Ingraham <stoa@gmx.us> wrote:
On Thu, Mar 01, 2018 at 08:13:08PM +0100, ProgAndy wrote:
Am 01.03.2018 um 00:41 schrieb Dutch Ingraham:
On Wed, Feb 28, 2018 at 04:54:03PM -0600, Doug Newgard via arch-general wrote:
On Wed, 28 Feb 2018 12:43:26 -0600 Dutch Ingraham <stoa@gmx.us> wrote:
On Wed, Feb 28, 2018 at 11:50:09AM -0600, Doug Newgard via arch-general wrote:
You're looking at the dates that the last *bundle* was released. That says nothing about what firmware is available for your processor. Your microcode was "updated early", so it is being loaded just fine.
Scimmia Thanks, Scimmia. I had considered that, but thought that would have been spelled-out somewhere on Intel's site and didn't want to just assume. So, how does one determine what files are on the .img? The img file can be extracted with bsdtar. iucode_tool in the AUR used for working with the intel bin file inside of that .img file. It can list, extract, search, and more. There's even an example on the Microcode wiki page.
Did you just add that wiki page information?? (I'm just kidding, of course.) Totally missed it - thanks for the info!
In February Intel also released a PDF with available and planned microcode updates. The original now asks for a login, but this is a mirror:
http://www-pc.uni-regensburg.de/systemsw/security/ microcode-update-guidance_02122018.pdf
Original location: https://newsroom.intel.com/wp-content/uploads/sites/11/2018/ 02/microcode-update-guidance.pdf
That's excellent information. Apparently, my 8 year old Core2 may soon be getting its first MCU!
-- mike c
That's excellent information. Apparently, my 8 year old Core2 may soon be getting its first MCU!
My apologies for top posting - it was accidental. There is a newer version of that file dated February 26th but I can't remember where I downloaded it from. I've put it at https://filebin.net/q3s5in117kp7mkut/microcode-update-guidance.pdf if you want to see it. -- mike c
On Fri, Mar 02, 2018 at 08:10:45PM +0000, Mike Cloaked via arch-general wrote:
There is a newer version of that file dated February 26th but I can't remember where I downloaded it from.
I've put it at https://filebin.net/q3s5in117kp7mkut/microcode-update-guidance.pdf if you want to see it.
Thanks - I'll take a look.
participants (5)
-
Doug Newgard
-
Dutch Ingraham
-
Mike Cloaked
-
ProgAndy
-
Ralf Mardorf