From: Gene Heskett <gene.heskett@verizon.net>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
tigran@aivazian.fsnet.co.uk,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: Linux* Processor Microcode Data File
Date: Mon, 09 Mar 2009 13:03:31 -0400 [thread overview]
Message-ID: <200903091303.32022.gene.heskett@verizon.net> (raw)
In-Reply-To: <20090309162416.GC24213@silver.sucs.org>
On Monday 09 March 2009, Sitsofe Wheeler wrote:
>At the risk of being wrong twice in a row...
>
>On Mon, Mar 09, 2009 at 11:58:22AM -0400, Gene Heskett wrote:
>> I'll have to admit it was with some trepidation that I might brick my
>> processor, which is a quad core AMD 9550, stepping 03 running at 2.2 ghz,
>> but
>
>Microcode patching in this particular fashion (i.e. _not_ updating the
>BIOS but "on the fly") is volatile (so it has to be redone at every
>boot) which should mean it is very hard to brick a machine this way as
>rebooting will undo everything. Of course someone is going to tell me
>how they managed to kill a machine stone dead due to some sequence of
>events I hadn't thought of and I disclaim any responsiblity if someone
>tries to update their microcode and harms their machine in any fashion -
>you update at your own risk :).
>
>> the directions didn't note until the end, that it would take a 2.6.29
>> series kernel to do it and I was running 2.6.28.7. But when I got to the
>> modprobe -r microcode, modprobe microcode part, there was no feedback from
>> either command. So did I, or did I not do this as I was and am running
>> 2.6.28.7? The following was reported in my log:
>
>modprobe generally doesn't return much if the module in question loads
>or (as in this case because you were using -r) is removed. That's the
>typical Unix command line behviour - no response/output on "OK".
>
>> 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.863101] microcode: size 1936, total_size 960 Mar 9
>> 07:22:04 coyote kernel: [65725.863107] microcode: CPU3 patch does not
>> match (processor_rev_id: 1020, eqiv_cpu_id: 1022) Mar 9 07:22:04 coyote
>> kernel: [65725.863110] microcode: size 968, total_size 960 Mar 9 07:22:04
>> coyote kernel: [65725.863120] microcode: CPU3 updated from revision
>> 0x1000065 to 0x1000083 Mar 9 07:22:04 coyote kernel: [65725.863122]
>> Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
>>
>> Inquiring minds and all that. Comments please?
>
>It looks like the firmware file (amd-ucode/microcode_amd.bin) doesn't
>match your processor. CC'ing Andreas for comment as you have an AMD
>machine...
Thank You. But the text report above also says it did update it, hence the
confusion.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
For fast-acting relief, try slowing down.
next prev parent reply other threads:[~2009-03-09 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 9:43 Dragoslav Zaric
2009-03-09 10:00 ` Jike Song
2009-03-09 10:30 ` Andreas Herrmann
2009-03-09 14:16 ` Sitsofe Wheeler
2009-03-09 15:11 ` Arjan van de Ven
2009-03-09 15:34 ` Sitsofe Wheeler
2009-03-09 15:58 ` Gene Heskett
2009-03-09 16:24 ` Sitsofe Wheeler
2009-03-09 17:03 ` Gene Heskett [this message]
2009-03-09 17:57 ` Andreas Herrmann
2009-03-09 16:53 ` Arjan van de Ven
2009-03-12 10:03 ` Giacomo A. Catenazzi
2009-03-12 14:07 ` Arjan van de Ven
2009-03-13 8:37 ` Giacomo A. Catenazzi
[not found] ` <2d05c4580903130142o2e5ebbcfw1e35eb52ea48e4b1@mail.gmail.com>
2009-03-13 8:44 ` Dragoslav Zaric
2009-03-13 14:55 ` Gene Heskett
2009-03-12 14:53 ` Dragoslav Zaric
2009-03-09 14:27 ` Arjan van de Ven
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=200903091303.32022.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=andreas.herrmann3@amd.com \
--cc=arjan@infradead.org \
--cc=dragoslav.zaric.kd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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®