Date: Tue, 3 Jul 2018 10:27:06 +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: <ece2a01d-6a37-0325-3c2d-f6682bb391e1@ingresso.co.uk> In-Reply-To: <20180701105540.GX2430@kib.kiev.ua> References: <20180630165508.GT2430@kib.kiev.ua> <E1fZZOe-0001FU-I7@dilbert.ingresso.co.uk> <20180701105540.GX2430@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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:
cpucontrol -m '0xc0011029|=0x2000' $x
cpucontrol -m '0xc0011020|=0x10' $x
but it does not do these bits:
cpucontrol -m '0xc0011028|=0x10' $x
cpucontrol -m '0xc0011020|=0x200000000000000' $x
(though someone else might want to doubel check that as I may have
miscounted the bits!)
am going to trey your patch today
-pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ece2a01d-6a37-0325-3c2d-f6682bb391e1>