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 at sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
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.