[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090309175746.GB20716@alberich.amd.com>
Date: Mon, 9 Mar 2009 18:57:46 +0100
From: Andreas Herrmann <andreas.herrmann3@....com>
To: Sitsofe Wheeler <sitsofe@...oo.com>
CC: Gene Heskett <gene.heskett@...izon.net>,
Arjan van de Ven <arjan@...radead.org>,
Dragoslav Zaric <dragoslav.zaric.kd@...il.com>,
LKML <linux-kernel@...r.kernel.org>, tigran@...azian.fsnet.co.uk
Subject: Re: Linux* Processor Microcode Data File
On Mon, Mar 09, 2009 at 04:24:16PM +0000, Sitsofe Wheeler wrote:
> On Mon, Mar 09, 2009 at 11:58:22AM -0400, Gene Heskett wrote:
> > Mar 9 07:22:04 coyote kernel: [65725.855365] platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
...
> > Mar 9 07:22:04 coyote kernel: [65725.863107] microcode: CPU3 patch
> > does not match (processor_rev_id: 1020, eqiv_cpu_id: 1022) is
> > printed.
This line should better be a debug message. There can be several
ucode-patches in amd-ucode/microcode_amd.bin. The kernel code checks
whether those patches match the CPU revision and if a patch doesn't
match, one such a line shows up. (which is ... obfuscating)
I'll fix this asap in mainline, but IMHO it's not worth to fix this in
.28.
> > Mar 9 07:22:04 coyote kernel: [65725.863120] microcode: CPU3
> > updated from revision 0x1000065 to 0x1000083
Finally CPU microcode was updated as this message is indicating.
Regards,
Andreas
PS: You can check the microcode patch level of your AMD family 10h and
11h CPU by reading MSR 0x0000008b. E.g. using lsmsr from x86info
package shows
# lsmsr -r 0x0000008b -c 0
PATCH_LEVEL = 0x0000000001000065
--
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
--
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/
Powered by blists - more mailing lists