From: Borislav Petkov <bp@alien8.de>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: Seeing the microcode revision in /proc/cpuinfo
Date: Tue, 14 Aug 2012 15:12:11 +0200 [thread overview]
Message-ID: <20120814131211.GA25921@x1.osrc.amd.com> (raw)
In-Reply-To: <502A623C020000A10000BACA@gwsmtp1.uni-regensburg.de>
On Tue, Aug 14, 2012 at 02:35:40PM +0200, Ulrich Windl wrote:
> Hi!
>
> 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".
>
> 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
>
> Does that mean the revision is 0x14 BEFORE or AFTER the microcode update?
>
> Wouldn't you agree that seeing the microcode revision in /proc/cpuinfo would be nice?
Well, you must be using an old-ish kernel because the microcode revision
infact *is* in /proc/cpuinfo:
processor : 1
...
stepping : 0
microcode : 0x5000028
This is on 3.6-rc1 and that functionality is upstream since 3.2.
HTH.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-08-14 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 12:35 Ulrich Windl
2012-08-14 13:12 ` Borislav Petkov [this message]
2012-08-14 13:20 ` Antw: " Ulrich Windl
2012-08-14 13:31 ` Borislav Petkov
2012-08-14 15:30 ` Henrique de Moraes Holschuh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120814131211.GA25921@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome