Date: Tue, 24 Apr 2018 15:01:35 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Mike Tancsa <mike@sentex.net>, 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: <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> In-Reply-To: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> References: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk> <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/04/2018 14:56, Mike Tancsa wrote: > 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. Well, I ranh the iperf tests between real machine for 24 hours and that worked fine. I also then spun up a Virtualbox with Win10 in it, and ran iuperf to there at the same time as doing it betwene real machines, and also did a full virus scan to exercise the disc. the idea being to replicate Mondays lockup. But its all fine - the only differece being that I have disabled SMT again. Do you get lockup-s with SMT disabled ? I dint have any experince with bhyve and dont have the tiime to start learning right now, hence me testing with VB, which I already have pa nd running. I can repeat with SMt on again to veiry that it does then lock up. All very odd though - am pleased its stable, but dissapinted at the amout of stuff I have had to turn off to get it to that state. -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84898b9f-991c-420a-3ebd-f8c4ad9915e1>