From owner-freebsd-stable@freebsd.org Mon Jun 18 19:50:30 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 21CFF101D7A3 for ; Mon, 18 Jun 2018 19:50:30 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (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 BD6CF6F3A1; Mon, 18 Jun 2018 19:50:29 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 583A65646E; Mon, 18 Jun 2018 14:50:28 -0500 (CDT) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , Mike Tancsa , truckman@FreeBSD.org Cc: freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> From: Eric van Gyzen Openpgp: preference=signencrypt Message-ID: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> Date: Mon, 18 Jun 2018 14:50:27 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 19:50:30 -0000 On 06/18/2018 09:34, Pete French wrote: > Preseumably in the slightly longer term these workarounds go into the > actual kernel if it detects Ryzen ? Yes, Kostik said he would code this into the kernel after he gets enough feedback. Eric