mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Gene Heskett <gheskett@wdtv.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd microcode broken by 3.12.0?
Date: Sun, 29 Dec 2013 02:44:29 +0100	[thread overview]
Message-ID: <20131229014428.GA6041@nazgul.tnic> (raw)
In-Reply-To: <201312281137.12524.gheskett@wdtv.com>

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.

      reply	other threads:[~2013-12-29  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 16:37 Gene Heskett
2013-12-29  1:44 ` Borislav Petkov [this message]

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=20131229014428.GA6041@nazgul.tnic \
    --to=bp@alien8.de \
    --cc=gheskett@wdtv.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®