From owner-freebsd-current@freebsd.org Thu Jun 14 15:04:11 2018 Return-Path: Delivered-To: freebsd-current@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 7E819100BD7C for ; Thu, 14 Jun 2018 15:04:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0A1506F0E9 for ; Thu, 14 Jun 2018 15:04:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BE73B100BD76; Thu, 14 Jun 2018 15:04:10 +0000 (UTC) Delivered-To: current@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 ACEF7100BD75 for ; Thu, 14 Jun 2018 15:04:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 0B5AA6F0E8 for ; Thu, 14 Jun 2018 15:04:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5EF3s2a014240; Thu, 14 Jun 2018 18:03:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5EF3s2a014240 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5EF3shq014239; Thu, 14 Jun 2018 18:03:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 14 Jun 2018 18:03:54 +0300 From: Konstantin Belousov To: Mike Tancsa Cc: Eric van Gyzen , current@freebsd.org Subject: Re: Ryzen public erratas Message-ID: <20180614150354.GB2493@kib.kiev.ua> References: <20180613103535.GP2493@kib.kiev.ua> <231dda70-6383-9d5c-d6c3-98e1c784f505@vangyzen.net> <402ba93e-4930-4237-dd53-d20a24b317e3@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <402ba93e-4930-4237-dd53-d20a24b317e3@sentex.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 15:04:11 -0000 On Thu, Jun 14, 2018 at 10:24:17AM -0400, Mike Tancsa wrote: > On 6/14/2018 9:36 AM, Eric van Gyzen wrote: > > On 06/13/2018 05:35, Konstantin Belousov wrote: > >> Today I noted that AMD published the public errata document for Ryzens, > >> https://developer.amd.com/wp-content/resources/55449_1.12.pdf > >> > >> Some of the issues listed there looks quite relevant to the potential > >> hangs that some people still experience with the machines. I wrote > >> a script which should apply the recommended workarounds to the erratas > >> that I find interesting. > >> > >> To run it, kldload cpuctl, then apply the latest firmware update to your > >> CPU, then run the following shell script. Comments indicate the errata > >> number for the workarounds. > >> > >> Please report the results. If the script helps, I will code the kernel > >> change to apply the workarounds. > > Kostik: This thread on the -stable list has a lot of positive feedback: > > > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089110.html > > I have a couple of Epyc boxes that showed the same lockup behaviour. I > will re-install FreeBSD on them and see if their microcode updates fix > this issue as well... I am not sure about only microcode update. Depending on the BIOS vendor and current BIOS, you may need all three: BIOS update, microcode update using cpucontrol/devcpu-data, and running the script I posted. In the best case, some of this is just redundand. > > Should I run the same cpuctl commands on those CPUs ? BTW, I am happy > to loan one out to you in the FreeBSD netperf cluster for a few weeks > > ---Mike > > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada