From owner-freebsd-current@freebsd.org Sun Oct 21 17:33:39 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 C1CFEFFBCF9 for ; Sun, 21 Oct 2018 17:33:39 +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 1D47E711EF for ; Sun, 21 Oct 2018 17:33:39 +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 w9LHXStk003844 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Oct 2018 20:33:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9LHXStk003844 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w9LHXRgW003843; Sun, 21 Oct 2018 20:33:27 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 21 Oct 2018 20:33:27 +0300 From: Konstantin Belousov To: Hannes Hauswedell Cc: freebsd-current@freebsd.org Subject: Re: Current status of Ryzen (non-)support Message-ID: <20181021173327.GJ5335@kib.kiev.ua> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home 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: Sun, 21 Oct 2018 17:33:39 -0000 On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: > Hi everyone, > > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. > > 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.html 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. For now you can only get fixes for microcode from your BIOS updates. > * no full system freezes, but under load, e.g. building with 12 threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues Or look at the Linux sources and see if any workarounds are applied and chicken bits are set for your CPU. > > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation CPUs... > > Thanks and regards, > Hannes >