From owner-freebsd-stable@freebsd.org  Sun Jun  3 17:10:21 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 76E9CFE09A3
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun,  3 Jun 2018 17:10:21 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1D3B66F803;
 Sun,  3 Jun 2018 17:10:20 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from [82.47.240.30] (helo=foula.drayhouse.twisted.org.uk)
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fPWWG-0002WB-GP; Sun, 03 Jun 2018 17:10:16 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Mike Tancsa <mike@sentex.net>, Don Lewis <truckman@FreeBSD.org>
Cc: eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com,
 avg@freebsd.org
References: <tkrat.e96200e0b688ca3c@FreeBSD.org>
 <E1fP2HW-000HG4-KR@dilbert.ingresso.co.uk>
 <tkrat.5527722618de87c7@FreeBSD.org>
 <d32a66f4-2795-831e-6f4d-8d299ebfdbea@sentex.net>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <0e8b197f-15b2-b865-b532-cee2a20f2b42@ingresso.co.uk>
Date: Sun, 3 Jun 2018 18:10:30 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <d32a66f4-2795-831e-6f4d-8d299ebfdbea@sentex.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.26
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: Sun, 03 Jun 2018 17:10:21 -0000


> The compile bug has been fixed for me.  However, last I checked I can
> still freeze a system by generating a lot of network traffic between VMs
> in either bhyve or virtbox.  Its been a while since I tested (couple of
> months) but I dont recall anything obviously committed that highlighted
> that issue.  Note this is on Epyc and Ryzen boxes

Yes, it was your iperf3 tests which enable me to freeze the system with
SMP enabled. With SMP disabled it works fine, however. have you tried
that at all ? The only other settings I ahve are the global C-states
and cool-n-quiet being disabled. I dont really care about either so
havent tested re-enabling them.

-pete.