Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.announce.security > #2651

Re: Regarding microcode update

From Matus UHLAR - fantomas <uhlar@fantomas.sk>
Newsgroups linux.debian.user, linux.debian.announce.security
Subject Re: Regarding microcode update
Date 2018-03-26 17:30 +0200
Message-ID <vxCem-69n-7@gated-at.bofh.it> (permalink)
References <vxAvT-4N3-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


On 26.03.18 19:05, VigneshDhanraj G wrote:
>After microcode update, for signature=0x306a9 upgraded revision should be
>0x1f but dmesg shows wrong revision any ideas what went wrong.

according to the log, firmware was updated from 0x17 to 0x1b
which version of intel-microcode do you have installed?
did you reboot after upgrading the package?

>In intel release notes, came across the below notes which says that it
>should upgraded to 0x1f.
>IVB E2 6-3a-9:12 1c->1f
>
>dhanraj@debian:~$ dmesg | grep microcode
>[    2.542014] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x17
>[    2.543391] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.543971] microcode: CPU0 updated to revision 0x1b, date = 2014-05-29
>[    2.543997] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x17
>[    2.545378] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.545647] microcode: CPU1 updated to revision 0x1b, date = 2014-05-29
>[    2.545674] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x17
>[    2.547079] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.547357] microcode: CPU2 updated to revision 0x1b, date = 2014-05-29
>[    2.547366] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x17
>[    2.548655] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.548920] microcode: CPU3 updated to revision 0x1b, date = 2014-05-29
>[    2.548942] microcode: CPU4 sig=0x306a9, pf=0x2, revision=0x17
>[    2.550180] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.550460] microcode: CPU4 updated to revision 0x1b, date = 2014-05-29
>[    2.550480] microcode: CPU5 sig=0x306a9, pf=0x2, revision=0x17
>[    2.551675] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.551957] microcode: CPU5 updated to revision 0x1b, date = 2014-05-29
>[    2.551978] microcode: CPU6 sig=0x306a9, pf=0x2, revision=0x17
>[    2.553162] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.553429] microcode: CPU6 updated to revision 0x1b, date = 2014-05-29
>[    2.553435] microcode: CPU7 sig=0x306a9, pf=0x2, revision=0x17
>[    2.554585] platform microcode: firmware: agent loaded
>intel-ucode/06-3a-09 into memory
>[    2.554851] microcode: CPU7 updated to revision 0x1b, date = 2014-05-29
>[    2.554898] microcode: Microcode Update Driver: v2.00 <
>tigran@aivazian.fsnet.co.uk>, Peter Oruba
>
>Need to understand what went wrong in my side.
>
>Regards,
>Vigneshdhanraj

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
There's a long-standing bug relating to the x86 architecture that
allows you to install Windows.   -- Matthew D. Fuller

Back to linux.debian.announce.security | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Regarding microcode update VigneshDhanraj G <vigneshdhanraj.g@gmail.com> - 2018-03-26 15:40 +0200
  Re: Regarding microcode update Matus UHLAR - fantomas <uhlar@fantomas.sk> - 2018-03-26 17:30 +0200

csiph-web