From owner-freebsd-stable@freebsd.org  Fri Aug 10 22:34:07 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 A809B1076E2D
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 10 Aug 2018 22:34:07 +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 47E8A7E1DA
 for <freebsd-stable@freebsd.org>; Fri, 10 Aug 2018 22:34:07 +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 1foFyu-0006k7-Be
 for freebsd-stable@freebsd.org; Fri, 10 Aug 2018 22:34:04 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: freebsd-stable@freebsd.org
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>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <50ae7040-b0c4-4092-c5d0-75ed86ed4845@ingresso.co.uk>
Date: Fri, 10 Aug 2018 23:34:03 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0)
 Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <76f693ec-d6f5-4261-ac25-13100f4b2f5f@ingresso.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.27
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: Fri, 10 Aug 2018 22:34:07 -0000


So, having been stable for quite sme time, I have had three lockups on 
my Ryzen in the last week. two were whilst I was in X11, but one 
happened over the weekend whilst I was looged out, and thus I could get 
a screenshot of what was on the console when I got in this morning:

https://www.twisted.org.uk/~pete/ryzen_crash_img_20180810_104231.jpg

Don't know if thats of any help. I noticed a new BIOS came out very 
recently, and I have updated my motherboard to that today, but these 
lockups did happen after quite a long period of stability, which 
surprises me.

-pete.