Date: Fri, 23 Feb 2018 16:00:18 -0500 From: Nimrod Levy <nimrodl@gmail.com> To: Mike Tancsa <mike@sentex.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) Message-ID: <CAMgUhppBHroW1dAs2R7Bg_Dj1ZDCbz8xb8F5n0atjE4H31oPSg@mail.gmail.com> In-Reply-To: <4968b74b-47d1-4742-9e59-a26572f8276c@sentex.net> References: <a687883a-b2a8-5b18-f63e-754a2ed445c0@sentex.net> <bbcc09cf-0072-8510-156f-5c20c301d43f@sentex.net> <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <CAMgUhpo1C_0L86Xkzmuz5%2Be3C3zk5RNkVS9aEBEwF-2XZ4d1sQ@mail.gmail.com> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> <CAMgUhpohQBJ1as3V7M3girPPFiw5vsT7asZGzHWCv47cm2YU%2BQ@mail.gmail.com> <4968b74b-47d1-4742-9e59-a26572f8276c@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mike@sentex.net> wrote: > 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 > > <https://reviews.freebsd.org/D14347>; pulled in. > > > > I've also lowered the memory clock and disabled c-states in the bios. > > > > The bhyve VM is running CentOS. > > > > The system has been up for over 6 days and has been running the iperf3 > > loop for over 2 hours. > > > > The hardware is an Asus prime B350-Plus with a Ryzen 5 1600 and 32G of > RAM. > > Hmmm, Interesting. Thank you for testing. I have a slightly different > chipset (X370-PRO). Wouldnt think that would make a difference. And > considering the Epyc also crashes-- although that takes a LOT longer, I > am not sure whats going on. > > There is yet another BIOS update for this board. So trying with that. > The vmm driver does report things a little different, so we will see > > ivhd0: <AMD-Vi/IOMMU ivhd with EFR> on acpi0 > ivhd0: Flag:b0<IotlbSup,Coherent> > ivhd0: Features(type:0x11) MsiNumPPR = 0 PNBanks= 2 PNCounters= 0 > ivhd0: Extended features[31:0]:22294ada<PPRSup,NXSup,GTSup,IASup> HATS = > 0x2 GATS = 0x0 GLXSup = 0x1 SmiFSup = 0x1 SmiFRC = 0x2 GAMSup = 0x1 > DualPortLogSup = 0x2 DualEventLogSup = 0x2 > ivhd0: Extended features[62:32]:f77ef<USSup> Max PASID: 0x2f > DevTblSegSup = 0x3 MarcSup = 0x1 > ivhd0: supported paging level:7, will use only: 4 > ivhd0: device range: 0x0 - 0xffff > ivhd0: PCI cap 0x190b640f@0x40 feature:19<IOTLB,EFR,CapExt> > > The load also matters. Try with 2 FreeBSD instances. I am not able to > quickly crash with just one. > > ---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?CAMgUhppBHroW1dAs2R7Bg_Dj1ZDCbz8xb8F5n0atjE4H31oPSg>