From owner-freebsd-current@freebsd.org Tue Oct 23 03:27:12 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 3E08BFFDC48 for ; Tue, 23 Oct 2018 03:27:12 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8C3B85A68 for ; Tue, 23 Oct 2018 03:27:11 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from [10.153.163.240] (mobile-166-171-184-58.mycingular.net [166.171.184.58]) (authenticated bits=0) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTPSA id w9N3NZYs028106 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 22 Oct 2018 23:23:49 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Mon, 22 Oct 2018 23:23:51 -0400 (EDT) Mime-Version: 1.0 (1.0) Subject: Re: Current status of Ryzen (non-)support From: Daniel Eischen X-Mailer: iPhone Mail (16A405) In-Reply-To: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Date: Mon, 22 Oct 2018 23:23:32 -0400 Cc: freebsd-current@freebsd.org Message-Id: <7E247566-47FA-4BD7-ACBE-984C0DB9AC2D@freebsd.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> To: Hannes Hauswedell Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 23 Oct 2018 03:27:12 -0000 Sent from my iPhone > On Oct 22, 2018, at 6:00 PM, Hannes Hauswedell wro= te: >=20 >> On 21.10.18 19:33, Konstantin Belousov wrote: >>> On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: >>> Hi everyone, >>>=20 >>> I wanted to ask what the current status of Ryzen support is and/or >>> whether any new changes are planned. >>>=20 >>> My situation: >>> * second generation Ryzen: 2600X >>> * running -CURRENT >>> * I have done the things described here: >>> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.htm= l >> This was based on the public errata document for the first gen ryzen. >> I am not aware of the erratas ('revision guides' in AMD terminology) >> for the second gen ryzens. Coming in a little late on this thread, just upgraded my 10 year old system t= o an AMD Ryzen 5 2400G. I noticed that the link below, and alluded to in th= e above pipermail link, does mention the 2nd gen Ryzen processors. Apologie= s if I misunderstood the above response. https://developer.amd.com/wp-content/resources/55449_1.12.pdf Also, my cpuid (Id=3D0x810f10 Family=3D0x17 Model=3D0x11) isn't mentioned i= n the above errata, so I guess it's not quite up to date for more recent 2nd= gen Ryzen, even though the 2400G was released months before the dated errat= a. I've not applied any of the sysctls mentioned in the above email, but have u= pdated my BIOS to the latest (ASUS X470-PRO). I've not experienced any prob= lems in several j8 buildworlds or poudriere runs (building roughly 1000 port= s). -- DE=