From owner-freebsd-virtualization@freebsd.org Tue Mar 13 15:33:37 2018 Return-Path: Delivered-To: freebsd-virtualization@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 A5E8A36B for ; Tue, 13 Mar 2018 15:33: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 4A3B6836BB; Tue, 13 Mar 2018 15:33:37 +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 w2DFXale077189 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Mar 2018 11:33:36 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w2DFXYlP061152; Tue, 13 Mar 2018 11:33:34 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) To: Peter Grehan , Anish , "pholes@sentex.net" , "freebsd-virtualization@freebsd.org" References: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> <2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb@freebsd.org> <48768738-e699-fd06-9154-9b5be1bbabcc@sentex.net> <36c062e4-352b-eebe-5f08-1af250d98eee@sentex.net> <7fa0b7a0-492e-6ded-3b5c-1edeff54d746@sentex.net> <7f599ae6-4de6-4a65-5a03-7e41f5f72530@freebsd.org> <92443071-e9b7-4941-16f3-5d5c423f4d0a@sentex.net> <1b0bb7de-5e12-8b7c-3d5a-93570852d0f2@sentex.net> <87431121-b7fb-1a5c-7081-d76347c27e53@freebsd.org> From: Mike Tancsa Organization: Sentex Communications Message-ID: <493a7783-dac5-5fb0-4ab8-b1a576fb9379@sentex.net> Date: Tue, 13 Mar 2018 11:33:35 -0400 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: <87431121-b7fb-1a5c-7081-d76347c27e53@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 15:33:37 -0000 On 3/6/2018 2:42 PM, Peter Grehan wrote: >>     Would virtualbox do this too (send a lot of IPIs)? I first noticed >> the >> lockups using it and not bhyve.  I have been using bhyve now as its >> easier to script the lockups etc. > >  Yes it would. Hmmm, this makes it even more mysterious. > >  I'll go and have a look a the FreeBSD interface code for VBox to see if > anything stands out in the way it uses IPIs. > >  It doesn't use the optimized i/f that bhyve uses, so this points to it > being a more general problem. Hi Peter, I have been stress testing the box without any hypervisor software loaded and all seems pretty stable. I left parallel buildworlds running along with a few background jobs of dd if=/dev/urandom count=10000 | sha256 randomly running in the background for 24hrs. I am now running the buildworlds along with maxing out the network card with bidirectional traffic. Its been up for 6days without issue. Any other thoughts / tests I can do to try and help narrow down this issue ? ---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