linux-kernel - Re: amd microcode broken by 3.12.0?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20131229014428.GA6041@nazgul.tnic>
Date:	Sun, 29 Dec 2013 02:44:29 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Gene Heskett <gheskett@...v.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: amd microcode broken by 3.12.0?

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@...azian.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.
--
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/