From owner-freebsd-stable@freebsd.org Thu Jun 14 10:30:11 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 5AB98101A3E2 for ; Thu, 14 Jun 2018 10:30:11 +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 F058882A05; Thu, 14 Jun 2018 10:30:10 +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 1fTPW1-000NIL-Un; Thu, 14 Jun 2018 10:30:05 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fTPW1-0000sG-Oa; Thu, 14 Jun 2018 11:30:05 +0100 To: mike@sentex.net, petefrench@ingresso.co.uk, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com In-Reply-To: <92fd230d-f99a-185d-a2c0-c84eed5b8bc5@sentex.net> Message-Id: From: Pete French Date: Thu, 14 Jun 2018 11:30:05 +0100 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: Thu, 14 Jun 2018 10:30:11 -0000 > Check out this thread on current. I re-ran the tests I did in Feb to > lockup the Ryzen box, and they are ok now with the latest micro code > updates from AMD. I will let the tests run a good 48hrs, but in the > past it would only take 5-10 min to cause a hard lockup > > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html Ah, excellent, tanksf for the pinter. I was already running the latest microcode, but have also now flashed my BIOS and applied the shell script fixes from that thread. Will try running with SMT re-enabled next week, as I need the machine not to lockup the next few days when I am not in the office, but it looks very promising. -pete.