Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?)

Looks like I got almost 4 full weeks before it locked up this morning :( On Fri, Feb 23, 2018 at 3:33 PM Nimrod Levy wrote: > After a couple of hours of running the iperf commands you were testing > with, I'm unable to duplicate this so far. > > I'm running with FreeBSD

Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?)

I'm not using any FreeBSD VMs, only on the bare metal host. The VM instance is CentOS. The network to the VM is a tap bridge. On Fri, Feb 23, 2018 at 3:44 PM, Mike Tancsa wrote: > On 2/23/2018 3:33 PM, Nimrod Levy wrote: > > After a couple of hours of running the iperf

Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?)

On 2/23/2018 3:33 PM, Nimrod Levy wrote: > After a couple of hours of running the iperf commands you were testing > with, I'm unable to duplicate this so far. > > I'm running with FreeBSD stable from 17-Feb with the commits noted > in https://reviews.freebsd.org/D14347 >

Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?)

After a couple of hours of running the iperf commands you were testing with, I'm unable to duplicate this so far. I'm running with FreeBSD stable from 17-Feb with the commits noted in https://reviews.freebsd.org/D14347 pulled in. I've also lowered the memory clock and disabled c-states in the