Date: Mon, 18 Jun 2018 09:59:34 -0400 From: Mike Tancsa <mike@sentex.net> To: Pete French <petefrench@ingresso.co.uk>, 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: <ea000302-b393-45b7-2f5d-4f3b9bddec5c@sentex.net> In-Reply-To: <E1fTPW1-0000sG-Oa@dilbert.ingresso.co.uk> References: <E1fTPW1-0000sG-Oa@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/14/2018 6:30 AM, Pete French wrote: >> Check out this thread on current. I re-ran the tests I did in Feb to >> lockup the Ryzen box, and they are ok now with the latest micro code >> updates from AMD. I will let the tests run a good 48hrs, but in the >> past it would only take 5-10 min to cause a hard lockup >> >> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > > Ah, excellent, tanksf for the pinter. I was already running the latest > microcode, but have also now flashed my BIOS and applied the shell > script fixes from that thread. Will try running with SMT re-enabled > next week, as I need the machine not to lockup the next few days > when I am not in the office, but it looks very promising. 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 https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html seem to have fixed the last issue I was seeing ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea000302-b393-45b7-2f5d-4f3b9bddec5c>