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] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Mar 2015 10:27:03 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Daniel J Blueman <daniel@...ascale.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Quentin Casasnovas <quentin.casasnovas@...cle.com>,
	Steffen Persvold <sp@...ascale.com>,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH] x86: Unbreak early processor microcode loading

On Thu, Mar 19, 2015 at 03:30:23PM +0800, Daniel J Blueman wrote:
> Neat; I added the 'amd-ucode/' directory prefix to the string and adjusted
> the buffer size, and the microcode is loaded,

We shouldn't need to do that though for obvious reasons.

IOW, you need to type in only the filenames of the microcode blobs in Kconfig
option:

CONFIG_EXTRA_FIRMWARE="microcode_amd.bin microcode_amd_fam15h.bin microcode_amd_fam16h.bin"

and then add the absolute path to them with:

CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/amd-ucode"

That worked here yesterday.

> but we see consistent hangs when onlining core 32 on the first server.

That's some system boundary, i.e. 4*8.

> Further investigation shows the BIOS in this platform isn't loading the
> microcode after the Hypertransport reconfig warm-boot (though other
> platforms do), so it's a better solution I engage with the vendor to fix
> their BIOS, rather than working around it in the kernel at this time.

Oh, most definitely!

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ