* amd microcode broken by 3.12.0?
@ 2013-12-28 16:37 Gene Heskett
2013-12-29 1:44 ` Borislav Petkov
0 siblings, 1 reply; 2+ messages in thread
From: Gene Heskett @ 2013-12-28 16:37 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Greetings;
Fresh build/boot of a PAE 3.12.0 on an AMD Phenom...
On checking dmesg, I see:
microcode: CPU0: patch_level=0x01000065
microcode: CPU1: patch_level=0x01000065
microcode: CPU2: patch_level=0x01000065
microcode: CPU3: patch_level=0x01000065
microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>,
Peter Oruba
Fairly late since I don't have early microcode checked in the .config.
FWIW, it didn't work when I had it checked either.
While booted to much older kernels, it reports that each cpu has been
brought up to patch level 0x01000083
So, stepping into /etc/init.d and doing a "sudo ./microcode_ctl", this is
returned:
./microcode_ctl: 90: gprintf: not found
Which has me scratching my head, wondering if my .config is screwed?
What is gprintf?
grepping .config for "print":
gene@coyote:~/src/linux-3.12.0$ grep -A5 print .config
# printk and dmesg options
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DYNAMIC_DEBUG is not set
config.gz is attached.
Thanks for any hints.
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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
When I was 16, I thought there was no hope for my father. By the time I
was
20, he had made great improvement.
A pen in the hand of this president is far more
dangerous than 200 million guns in the hands of
law-abiding citizens.
[-- Attachment #2: config-3.12.0.gz --]
[-- Type: application/x-gzip, Size: 28617 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: amd microcode broken by 3.12.0?
2013-12-28 16:37 amd microcode broken by 3.12.0? Gene Heskett
@ 2013-12-29 1:44 ` Borislav Petkov
0 siblings, 0 replies; 2+ messages in thread
From: Borislav Petkov @ 2013-12-29 1:44 UTC (permalink / raw)
To: Gene Heskett; +Cc: linux-kernel
On Sat, Dec 28, 2013 at 11:37:12AM -0500, Gene Heskett wrote:
> Greetings;
>
> Fresh build/boot of a PAE 3.12.0 on an AMD Phenom...
>
> On checking dmesg, I see:
>
> microcode: CPU0: patch_level=0x01000065
> microcode: CPU1: patch_level=0x01000065
> microcode: CPU2: patch_level=0x01000065
> microcode: CPU3: patch_level=0x01000065
> microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>,
> Peter Oruba
>
> Fairly late since I don't have early microcode checked in the .config.
I have a bunch of fixes for that:
http://marc.info/?l=linux-kernel&m=138628638215162
wanna give them a try?
> FWIW, it didn't work when I had it checked either.
>
> While booted to much older kernels, it reports that each cpu has been
> brought up to patch level 0x01000083
>
> So, stepping into /etc/init.d and doing a "sudo ./microcode_ctl", this is
> returned:
>
> ./microcode_ctl: 90: gprintf: not found
>
> Which has me scratching my head, wondering if my .config is screwed?
I don't think we ever did microcode update with the microcode_ctl on
AMD, did we? Hmmm.
In any case
echo 1 > /sys/devices/system/cpu/microcode/reload
should work.
HTH.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-12-29 1:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-28 16:37 amd microcode broken by 3.12.0? Gene Heskett
2013-12-29 1:44 ` Borislav Petkov
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®