From owner-freebsd-stable@freebsd.org Sat Apr 21 09:27:23 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 9DB16FB2872 for ; Sat, 21 Apr 2018 09:27:23 +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 4292B82810; Sat, 21 Apr 2018 09:27:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1f9one-000CD6-NL; Sat, 21 Apr 2018 09:27:18 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1f9one-0006n1-K6; Sat, 21 Apr 2018 10:27:18 +0100 To: mike@sentex.net, nimrodl@gmail.com, petefrench@ingresso.co.uk Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, truckman@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Sat, 21 Apr 2018 10:27:18 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2018 09:27:23 -0000 > Its not just the Ryzen, I can lock up Epyc CPUs as well. They take a bit > longer, but its not that hard to repeat. Unfortunately, I had to > allocate this hardware over the Linux where it works reliably under all > workloads without any such lock ups with all the default BIOS settings :( AH, thats a shame to hear - was hooing it had worked OK for you! > Here is a test case. > https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088433.html Will give that a try next week - when remote form the box I dont want to crash it, so no such tests at the weekend, but hen I am back will see. The lockup from Thursday was aan idle-lockup, and that hasnt happened since I chnaged the BIOS settings. May reenable those one at a time to see if any single one is reposible, unless anyone has any insight. Much hunch would be that SMT may be OK to re-enable as tat has nothing do do with loading, whcih the other two do. cheers, -pete.