From owner-freebsd-stable@freebsd.org  Wed Apr 25 00:04:45 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
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 A99D4FB7CA4
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 25 Apr 2018 00:04:45 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "amnesiac", Issuer "amnesiac" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 41C2C82465
 for <freebsd-stable@freebsd.org>; Wed, 25 Apr 2018 00:04:45 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org ([76.212.85.177])
 by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3P065x9042939
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Wed, 25 Apr 2018 00:06:06 GMT (envelope-from truckman@FreeBSD.org)
Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3P04VZc088649
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Tue, 24 Apr 2018 17:04:32 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Date: Tue, 24 Apr 2018 17:04:26 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Mike Tancsa <mike@sentex.net>
cc: Pete French <petefrench@ingresso.co.uk>, nimrodl@gmail.com,
 eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com,
 avg@freebsd.org
In-Reply-To: <e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2@sentex.net>
Message-ID: <tkrat.5235cb463511b830@FreeBSD.org>
References: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk>
 <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net>
 <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk>
 <e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2@sentex.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-Disposition: INLINE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 00:04:45 -0000

On 24 Apr, Mike Tancsa wrote:
> On 4/24/2018 10:01 AM, Pete French wrote:
>> 
>> 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.
> 
> I was able to lock it up with vbox. bhyve was just a little easier to
> script and also I figured would be good to get VBox out of the mix in
> case it was something specific to VBox.  I dont recall if I tried it
> with SMT disabled.  Regardless, on Intel based systems I ran these tests
> for 72hrs straight without issue.   I can sort of believe hardware issue
> or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but
> the fact that two server class MBs from SuperMicro along with an Epyc
> chip also does the same thing makes me think something specific to
> FreeBSD and this class of AMD CPU :(

It would be interesting to test other AMD CPUs.  I think AMD and Intel
have some differences in the virtualization implementations.