Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754960Ab2HNMfy (ORCPT ); Tue, 14 Aug 2012 08:35:54 -0400 Received: from rrzmta1.uni-regensburg.de ([194.94.155.51]:60584 "EHLO rrzmta1.uni-regensburg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754652Ab2HNMfs convert rfc822-to-8bit (ORCPT ); Tue, 14 Aug 2012 08:35:48 -0400 Message-Id: <502A623C020000A10000BACA@gwsmtp1.uni-regensburg.de> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Tue, 14 Aug 2012 14:35:40 +0200 From: "Ulrich Windl" To: Subject: Q: Seeing the microcode revision in /proc/cpuinfo Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1064 Lines: 24 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? For those CPUs lacking the feature one could hard-wire the value "none" (which would be also "kind of true")... Regards, Ulrich (not subscribed, so please CC: you replies to me) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/