From owner-freebsd-stable@freebsd.org  Mon Apr 23 09:44:29 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 EDEF1FAC8B4
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 23 Apr 2018 09:44:28 +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 8C7306AE22;
 Mon, 23 Apr 2018 09:44:28 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk)
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fAY1L-000OqU-LL; Mon, 23 Apr 2018 09:44:27 +0000
Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91
 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
 id 1fAY1L-000LPH-Ji; Mon, 23 Apr 2018 10:44:27 +0100
Date: Mon, 23 Apr 2018 10:44:27 +0100
To: petefrench@ingresso.co.uk, lists@eitanadler.com
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
Cc: truckman@freebsd.org, freebsd@hda3.com, freebsd-stable@freebsd.org,
 eric@vangyzen.net, avg@freebsd.org
References: <a9eef511-6478-b373-590e-086029b4f97b@vangyzen.net>
 <E1f9U0O-0002Bl-O7@dilbert.ingresso.co.uk>
 <CAF6rxgkgK1_9cWVV9WT6EE+oaioU_U=YYxoEr0N-n6VrehNg5g@mail.gmail.com>
In-Reply-To: <CAF6rxgkgK1_9cWVV9WT6EE+oaioU_U=YYxoEr0N-n6VrehNg5g@mail.gmail.com>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E1fAY1L-000LPH-Ji@dilbert.ingresso.co.uk>
From: Pete French <petefrench@ingresso.co.uk>
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: Mon, 23 Apr 2018 09:44:29 -0000

> I have a Ryzen system
> parts: https://pcpartpicker.com/list/HhycYT
> dmesg: http://dmesgd.nycbug.org/index.cgi?do=view&id=3516
>
> which I have been using for months without issue and on completely
> default settings.

Thats encouranging -= and I think you are the first person to report
that without any tweaking to the best of my recollection!

> What mobo do you have? Did you update the BIOS to the latest version?

MSI X370 Xpower Titanium - I upgraded to that one from my original choice
ater comments on this thread about power  which I hadnt considered (I
had also decided to buy a larger Ryzen 7). The BIOS is the latest version,
and I cleared CMOS to get the default settings. Memory is some Crucial
DDR4 3200 which is underclocked to 2133. This microprocessor itself
is a Ryzen 7 1700 (not X) which was made in week 33, so should not have the
hardware fault on it.

It's been stable over the weekend, as I posted in a different email, am
going to try and knock it over today with some tests if I can.

-pete.