Re: ANNOUNCEMENT: Intel processor microcode security update
* On 2013 07 Sep 16:40 -0500, Henrique de Moraes Holschuh wrote:
> On Sat, 07 Sep 2013, Nate Bargmann wrote:
> > I have an older P4 system with hyperthreading and it seems the updated
> > microcode was loaded when I installed the package:
>
> It was loaded, but the messages you sent do not imply an update took place.
> Check for microcode messages with "updated". If you find none, then your
> BIOS already has the latest version of the microcode.
>
> The Intel microcode update kernel driver first tells you what microcode is
> installed in the processor cores, THEN it tries to update them and outputs a
> messages about it if, and only if, it manages to actually update a core.
On a Core Duo box I see that it was updated upon installation:
Sep 7 12:33:04 agbox kernel: [429518.506682] microcode: CPU0
sig=0x1067a, pf=0x1, revision=0xa07
Sep 7 12:33:04 agbox kernel: [429518.525345] microcode: CPU1
sig=0x1067a, pf=0x1, revision=0xa07
Sep 7 12:33:04 agbox kernel: [429518.527817] microcode: Microcode
Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 7 12:33:04 agbox kernel: [429518.588010] microcode: CPU0 updated to
revision 0xa0b, date = 2010-09-28
Sep 7 12:33:04 agbox kernel: [429518.600013] microcode: CPU1 updated to
revision 0xa0b, date = 2010-09-28
I suppose there is no harm keeping the packages installed on systems
that currently aren't updating since, as you say, an update could come
along in the future.
Thanks for all the info, Henrique.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Ham radio, Linux, bikes, and more: http://www.n0nb.us
Reply to: