From owner-freebsd-stable@freebsd.org  Tue Jul  3 10:09:25 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 2AAA21031C06
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue,  3 Jul 2018 10:09:25 +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 94BF278726;
 Tue,  3 Jul 2018 10:09:24 +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 ESMTPS id w63A9FZV075316
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 3 Jul 2018 13:09:18 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w63A9FZV075316
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id w63A9Fst075315;
 Tue, 3 Jul 2018 13:09:15 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Tue, 3 Jul 2018 13:09:15 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Pete French <petefrench@ingresso.co.uk>
Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
Message-ID: <20180703100914.GC2430@kib.kiev.ua>
References: <20180630165508.GT2430@kib.kiev.ua>
 <E1fZZOe-0001FU-I7@dilbert.ingresso.co.uk>
 <20180701105540.GX2430@kib.kiev.ua>
 <ece2a01d-6a37-0325-3c2d-f6682bb391e1@ingresso.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ece2a01d-6a37-0325-3c2d-f6682bb391e1@ingresso.co.uk>
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-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 10:09:25 -0000

On Tue, Jul 03, 2018 at 10:27:06AM +0100, Pete French wrote:
> 
> > 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:
By 'it' you mean the microcode update/BIOS on your board ?

> 
> 
>          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.