Date: Thu, 27 Jul 2023 01:20:25 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Zenbleed Message-ID: <ZMGcKUIrqJ9TZZDo@kib.kiev.ua> In-Reply-To: <G8KdlREJ53JvhucNV2MkjySsZ4qqs6ZdHFXJaFqDIvXj5usSBEr3pOe29JoQVHgjtctmrIOR7O1PHwchvf_cGLr53jbwNGPy_F7_9OstBCE=@protonmail.com> References: <G8KdlREJ53JvhucNV2MkjySsZ4qqs6ZdHFXJaFqDIvXj5usSBEr3pOe29JoQVHgjtctmrIOR7O1PHwchvf_cGLr53jbwNGPy_F7_9OstBCE=@protonmail.com>
index | next in thread | previous in thread | raw e-mail
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.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZMGcKUIrqJ9TZZDo>