From owner-freebsd-stable@freebsd.org  Tue Jul  3 09:27:11 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 812E1102E2E4
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue,  3 Jul 2018 09:27:11 +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 1CCA07642A;
 Tue,  3 Jul 2018 09:27:11 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6])
 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 1faHaU-0002NP-Eo; Tue, 03 Jul 2018 09:27:06 +0000
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org
References: <20180630165508.GT2430@kib.kiev.ua>
 <E1fZZOe-0001FU-I7@dilbert.ingresso.co.uk>
 <20180701105540.GX2430@kib.kiev.ua>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <ece2a01d-6a37-0325-3c2d-f6682bb391e1@ingresso.co.uk>
Date: Tue, 3 Jul 2018 10:27:06 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180701105540.GX2430@kib.kiev.ua>
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: Tue, 03 Jul 2018 09:27:11 -0000


> It is very likely that the latest microcode sets the chicken bits for the
> known erratas already.  AFAIK, this is the best that a ucode update
> can typically do anyway.
>

I just did some testing - it does do these bits:


         cpucontrol -m '0xc0011029|=0x2000' $x
         cpucontrol -m '0xc0011020|=0x10' $x

but it does not do these bits:

         cpucontrol -m '0xc0011028|=0x10' $x
         cpucontrol -m '0xc0011020|=0x200000000000000' $x

(though someone else might want to doubel check that as I may have 
miscounted the bits!)

am going to trey your patch today

-pete.