From owner-freebsd-stable@freebsd.org  Mon Jan 29 00:11:51 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 B8436EC6DFA
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 29 Jan 2018 00:11:51 +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 5126975420
 for <freebsd-stable@freebsd.org>; Mon, 29 Jan 2018 00:11:51 +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 w0T0CJRk014551
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Mon, 29 Jan 2018 00:12:20 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 w0T0BfY9005315
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Sun, 28 Jan 2018 16:11:42 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Date: Sun, 28 Jan 2018 16:11:36 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ?
To: Pete French <petefrench@ingresso.co.uk>
cc: freebsd@hda3.com, nimrodl@gmail.com, freebsd-stable@freebsd.org,
 rroot@rootautomation.com
In-Reply-To: <c3f6f795-c50c-54cb-0ce7-1de1ea45575f@ingresso.co.uk>
Message-ID: <tkrat.7df4689bc4d593dc@FreeBSD.org>
References: <CADbMJxkx7=T3c1oaPnkARURQHoWL41m=6NbO8r327dAJq5BNAw@mail.gmail.com>
 <E1efpDh-000CgU-Ft@dilbert.ingresso.co.uk>
 <tkrat.bbbac53b7cddb2af@FreeBSD.org>
 <c3f6f795-c50c-54cb-0ce7-1de1ea45575f@ingresso.co.uk>
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: Mon, 29 Jan 2018 00:11:51 -0000

On 28 Jan, Pete French wrote:
> 
> 
> On 28/01/2018 20:28, Don Lewis wrote:
>> I'd be wary of the B350 boards with the higher TDP eight core Ryzen CPUs
>> since the VRMs on the cheaper boards tend to have less robust VRM
>> designs.
> 
> Gah! Yes, I forgot that.originally sec'd the board for a smaller Ryzen, 
> then though "what the hell" and got the 1700 without going back and 
> checking that kind of stuff. Hmm, shall swap for a different one if I 
> can. Thanks for poining that out.

I started off with a Gigabyte AB350 Gaming for my 1700X back when there
was enough ambiguity about ECC support to give me hope that it would
work.  Everything seemed to work other than ECC and the problems caused
by my buggy CPU and the shared page issue, but the VRM temps in the BIOS
were really high (and I had no way to monitor that under load).  When I
upgraded to get working ECC, I also looked at reviews about VRM quality.