From owner-freebsd-stable@freebsd.org  Wed Apr 25 09:14:09 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 3DE5CFC0EC8
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 25 Apr 2018 09:14:09 +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 D1CE77043D;
 Wed, 25 Apr 2018 09:14:08 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net
 ([82.47.237.48] 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 1fBGV3-0009eE-Al; Wed, 25 Apr 2018 09:14:05 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Don Lewis <truckman@FreeBSD.org>, Mike Tancsa <mike@sentex.net>
Cc: nimrodl@gmail.com, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, avg@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>
 <tkrat.5235cb463511b830@FreeBSD.org>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <3533f777-e708-623d-b280-5be418fd4d50@ingresso.co.uk>
Date: Wed, 25 Apr 2018 10:14:04 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <tkrat.5235cb463511b830@FreeBSD.org>
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.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 09:14:09 -0000


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

I've been using AMD CPU's pretty extensively since the early 90's - back 
then I was running NeXTStep and out of the three Intel alternatives it 
was the only one which ran properly. Never seen anything like this 
before now though. In particular this Ryzen replaces the CPU on an old 
Phenom II - i.e. its the same disc and hence the same OS and VirtualBox 
config - and that ran fine.

So theres something odd about the Ryzen here.

Am also not sure its to do with the virtualisation - I got my first 
lockup with no virtualisation going on at all. Disablign SMT and the 
system hasnt locked, despite heavy virtualbox use.

-pete.