linux-kernel - Re: Q: Seeing the microcode revision in /proc/cpuinfo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 14 Aug 2012 12:30:08 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Ulrich Windl <Ulrich.Windl@...uni-regensburg.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Q: Seeing the microcode revision in /proc/cpuinfo

On Tue, 14 Aug 2012, Ulrich Windl wrote:
> After several reboots due to memory errors after excellent power-saving of
> Linux on a HP DL380G7 with Intel Xeon 5650 processors (all in on memory
> bank), I found out the errate "BD104" and "BD123". The former should be
> fixed in a microcode revision "15H".

Hmm, BD104 is indeed nasty.  And that microcode update is not available
to the general public (i.e. through downloadcenter.intel.com).

> Now I wonder what microcode revision my CPUs currently have. /proc/cpuinfo
> doesn't show that, and the microcode update is a bit cryptic:
> 
> kernel: [   44.422912] microcode: CPU23 sig=0x206c2, pf=0x1, revision=0x14

You have revision 0x14.

Presumably, you will get revision 0x15 if you update the HP firmware in
that box.  The update you need was published by HP nearly an year ago.

> Does that mean the revision is 0x14 BEFORE or AFTER the microcode update?

Before.  The message you get when the CPU is updated is different.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/