Date: Tue, 24 Apr 2018 09:56:08 -0400 From: Mike Tancsa <mike@sentex.net> To: Pete French <petefrench@ingresso.co.uk>, nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> In-Reply-To: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk> References: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/23/2018 8:19 AM, Pete French wrote: > > All worked fine until just no,w when it did lockup. But the lockup > happened when I fired up VirtualBox as well on the Ryzen machine, had that > doing a lot of disc activity and also did a lot of ZFS activity on the box > itself. Which I find interesting, because your lockups were also happenng > when VirtualBox was running were they not ? > > So, am going to try that again (the iperf test and simultaneous Win10 > in VirtualBox), but with SMT off, to see if I can reproduce it. > I was doing the tests with bhyve, and the iperf tests were between VMs on the same box. That seems to trigger it fairly quickly. The Epyc took a bit more work, but I could reliable do it there too. ---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?59b435cf-f4fb-0cc8-3bd0-0765ac0592da>