mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
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 12:30:08 -0300	[thread overview]
Message-ID: <20120814153008.GA21885@khazad-dum.debian.net> (raw)
In-Reply-To: <502A623C020000A10000BACA@gwsmtp1.uni-regensburg.de>

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

      parent reply	other threads:[~2012-08-14 15:30 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
2012-08-14 13:20   ` Antw: " Ulrich Windl
2012-08-14 13:31     ` Borislav Petkov
2012-08-14 15:30 ` Henrique de Moraes Holschuh [this message]

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=20120814153008.GA21885@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --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

all inboxes | Powered by JetHome®