Date: Tue, 3 Jul 2018 13:06:16 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Konstantin Belousov <kostikbel@gmail.com> Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <343bb693-850b-92b0-9749-5c722b90f817@ingresso.co.uk> In-Reply-To: <20180703100914.GC2430@kib.kiev.ua> References: <20180630165508.GT2430@kib.kiev.ua> <E1fZZOe-0001FU-I7@dilbert.ingresso.co.uk> <20180701105540.GX2430@kib.kiev.ua> <ece2a01d-6a37-0325-3c2d-f6682bb391e1@ingresso.co.uk> <20180703100914.GC2430@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/07/2018 11:09, Konstantin Belousov wrote: > On Tue, Jul 03, 2018 at 10:27:06AM +0100, Pete French wrote: >> >>> It is very likely that the latest microcode sets the chicken bits for the >>> known erratas already. AFAIK, this is the best that a ucode update >>> can typically do anyway. >>> >> >> I just did some testing - it does do these bits: > By 'it' you mean the microcode update/BIOS on your board ? Yes, sorry. As I was testing without the patch I looked to see what the values were that it had set. I may have got my hex wrong on the last two though I have to say - it may be setting all four bits. -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?343bb693-850b-92b0-9749-5c722b90f817>