From owner-freebsd-stable@freebsd.org Fri Feb 23 20:44:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F7F8F1C997 for ; Fri, 23 Feb 2018 20:44:37 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C0B3477B9B for ; Fri, 23 Feb 2018 20:44:36 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w1NKiaj6027368 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 23 Feb 2018 15:44:36 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w1NKiXkJ010235; Fri, 23 Feb 2018 15:44:34 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) To: Nimrod Levy Cc: FreeBSD-STABLE Mailing List References: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <4968b74b-47d1-4742-9e59-a26572f8276c@sentex.net> Date: Fri, 23 Feb 2018 15:44:34 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Feb 2018 20:44:37 -0000 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 >  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: on acpi0 ivhd0: Flag:b0 ivhd0: Features(type:0x11) MsiNumPPR = 0 PNBanks= 2 PNCounters= 0 ivhd0: Extended features[31:0]:22294ada HATS = 0x2 GATS = 0x0 GLXSup = 0x1 SmiFSup = 0x1 SmiFRC = 0x2 GAMSup = 0x1 DualPortLogSup = 0x2 DualEventLogSup = 0x2 ivhd0: Extended features[62:32]:f77ef 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 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