From owner-freebsd-stable@freebsd.org Mon Jun 18 14:34:52 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 2D19C100B5D4 for ; Mon, 18 Jun 2018 14:34:52 +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 BE53981F3F; Mon, 18 Jun 2018 14:34:51 +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 ) id 1fUvF1-000IoT-FI; Mon, 18 Jun 2018 14:34:47 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa , truckman@FreeBSD.org Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com References: From: Pete French Message-ID: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> Date: Mon, 18 Jun 2018 15:34:47 +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: 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.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 14:34:52 -0000 On 18/06/2018 14:59, Mike Tancsa wrote: > FYI, both my Epyc and Ryzen system have been running 2+ days with the > tests that would normally hard lock the system in 5-60 min. The combo of > Microcode updates and system settings Thats for the update - I turned all the default motherboard settings back on when I got into work this morning, and it has been running fine so far. WIll run like this all week. > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > > seem to have fixed the last issue I was seeing Yes, those are the chnages I have applied. I went through that list over the weekend cross-referncing them to the errata document, and there are a couple of things in there which made me think 'aha!' - particularly the MWWAIT causing lockups on SMT, as it was disbling SMT that made it stable for me. I also have access to a cpuple of (virtualised) Epyc machines which I am going to run up later in the week and try the workarounds there. But it does look very much like its fixed, which is excellent. Preseumably in the slightly longer term these workarounds go into the actual kernel if it detects Ryzen ? -pete.