Messages in this thread | | | From | Gene Heskett <> | Subject | amd microcode broken by 3.12.0? | Date | Sat, 28 Dec 2013 11:37:12 -0500 |
| |
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. [unhandled content-type:application/x-gzip] | |