Date: Sun, 30 Jul 2023 16:45:56 +0000 From: Thomas Hurst <tom@hur.st> To: freebsd-security@freebsd.org Subject: Re: Zenbleed Message-ID: <ZMaTxBzby16y_G06@voi.aagh.net> In-Reply-To: <ZMGcKUIrqJ9TZZDo@kib.kiev.ua> References: <G8KdlREJ53JvhucNV2MkjySsZ4qqs6ZdHFXJaFqDIvXj5usSBEr3pOe29JoQVHgjtctmrIOR7O1PHwchvf_cGLr53jbwNGPy_F7_9OstBCE=@protonmail.com> <ZMGcKUIrqJ9TZZDo@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
* Konstantin Belousov (kostikbel@gmail.com) wrote: > On Wed, Jul 26, 2023 at 08:34:56PM +0000, 0x1eef wrote: > > Hello, > > > > I was curious if there are plans to apply the "chicken bit" > > workaround for the Ryzen line of processors. A firmware > > update is not scheduled to be released until Nov or Dec > > at the earliest. Thanks. > > The chicken bit workaround is > # for x in /dev/cpuctl*; do cpucontrol -m '0xc0011029|=0x200' $x; done > there is nothing to wait for. It is silly to push this into kernel when > recommended solution is ucode update. I created an rc script for this, including a check that the system is actually running a Zen 2 CPU: https://gist.github.com/Freaky/2560975d3c94246b86f464b8be75c967 -- Thomas 'Freaky' Hurst https://hur.st/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZMaTxBzby16y_G06>