From owner-freebsd-stable@freebsd.org  Tue Dec  4 20:10:55 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 6B153131AE09
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue,  4 Dec 2018 20:10:55 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 D9744706BE
 for <freebsd-stable@FreeBSD.org>; Tue,  4 Dec 2018 20:10:54 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <pi@freebsd.org>) id 1gUH21-000FYr-Qx
 for freebsd-stable@freebsd.org; Tue, 04 Dec 2018 21:10:57 +0100
Date: Tue, 4 Dec 2018 21:10:57 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: freebsd-stable@freebsd.org
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
Message-ID: <20181204201057.GP63752@home.opsec.eu>
References: <20180705133542.GG5562@kib.kiev.ua>
 <E1fb4mD-0006j7-SY@dilbert.ingresso.co.uk>
 <20180705145130.GH5562@kib.kiev.ua>
 <548b493e-6a51-32ca-b3c1-216cac037e8b@ingresso.co.uk>
 <20180727130016.GE2394@kib.kiev.ua>
 <76f693ec-d6f5-4261-ac25-13100f4b2f5f@ingresso.co.uk>
 <50ae7040-b0c4-4092-c5d0-75ed86ed4845@ingresso.co.uk>
 <0778a0b2-51b6-5c08-b777-cbeff7cae54f@ingresso.co.uk>
 <1f170eba-33de-0c79-9e6f-d18d5199e9fe@sentex.net>
 <276df722-7c6c-00c2-69ca-87efafac0448@sentex.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <276df722-7c6c-00c2-69ca-87efafac0448@sentex.net>
X-Rspamd-Queue-Id: D9744706BE
X-Spamd-Result: default: False [1.37 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_SPAM_LONG(0.62)[0.620,0];
 NEURAL_SPAM_MEDIUM(0.40)[0.401,0];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE];
 NEURAL_SPAM_SHORT(0.35)[0.352,0]
X-Rspamd-Server: mx1.freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Dec 2018 20:10:55 -0000

Hi!

> Well, another lockup. This time after ~ 10 days of uptime. Box was idle
> at the time and just a solid freeze.

Here's another datapoint: No lockups/problems with:

AMD Ryzen Threadripper 2950X
Board: PRIME X399-A (not the -PRO)
BIOS from 10/12/2018
running: 13.0-CURRENT r340445
up 19 days, running as a package builder

-- 
pi@FreeBSD.org         +49 171 3101372              2 years to go !