From owner-freebsd-stable@freebsd.org Sun Jul 1 10:15:59 2018 Return-Path: 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 21CA5FEEF76 for ; Sun, 1 Jul 2018 10:15:59 +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 AA9E689AC4; Sun, 1 Jul 2018 10:15:58 +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 ) id 1fZZOe-000HY4-KO; Sun, 01 Jul 2018 10:15:56 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fZZOe-0001FU-I7; Sun, 01 Jul 2018 11:15:56 +0100 To: kostikbel@gmail.com, petefrench@ingresso.co.uk Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org In-Reply-To: <20180630165508.GT2430@kib.kiev.ua> Message-Id: From: Pete French Date: Sun, 01 Jul 2018 11:15:56 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 10:15:59 -0000 > This should be the kernel patch equivalent to the script. Ah, thankyou. I shall give this a try on tuesday when I am physically back in front of the machine. I have been trying without the oath as you asked by the way, and with the latest microcode update (0x8001137) it also seems stable, without these tweaks. But I havent stressed it too much - if the errata says to set the bits then we should set the bits. > According to the revision document, some of the erratas are applicable > to the Ryzen 2, but I do not want to do the bit tweaking without a > confirmation. I was wndeting about that - but I dont have a Ryzen 2 to hand to test with unfortunately. Will let you know how the patch goes next week, thanks, -pete.