Date: Mon, 18 Jun 2018 15:34:47 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Mike Tancsa <mike@sentex.net>, truckman@FreeBSD.org Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> In-Reply-To: <ea000302-b393-45b7-2f5d-4f3b9bddec5c@sentex.net> References: <E1fTPW1-0000sG-Oa@dilbert.ingresso.co.uk> <ea000302-b393-45b7-2f5d-4f3b9bddec5c@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/06/2018 14:59, Mike Tancsa wrote: > FYI, both my Epyc and Ryzen system have been running 2+ days with the > tests that would normally hard lock the system in 5-60 min. The combo of > Microcode updates and system settings Thats for the update - I turned all the default motherboard settings back on when I got into work this morning, and it has been running fine so far. WIll run like this all week. > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > > seem to have fixed the last issue I was seeing Yes, those are the chnages I have applied. I went through that list over the weekend cross-referncing them to the errata document, and there are a couple of things in there which made me think 'aha!' - particularly the MWWAIT causing lockups on SMT, as it was disbling SMT that made it stable for me. I also have access to a cpuple of (virtualised) Epyc machines which I am going to run up later in the week and try the workarounds there. But it does look very much like its fixed, which is excellent. Preseumably in the slightly longer term these workarounds go into the actual kernel if it detects Ryzen ? -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69049a4c-cfb0-9a4f-9cdf-86e138301543>