From owner-freebsd-stable@freebsd.org Mon Apr 23 12:19:44 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 E4AEFFB777F for ; Mon, 23 Apr 2018 12:19:43 +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 889DE6D790; Mon, 23 Apr 2018 12:19:43 +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 1fAaRZ-000133-5j; Mon, 23 Apr 2018 12:19:41 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fAaRY-0000nB-Ut; Mon, 23 Apr 2018 13:19:41 +0100 To: nimrodl@gmail.com, petefrench@ingresso.co.uk, 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 Message-Id: From: Pete French Date: Mon, 23 Apr 2018 13:19:40 +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: Mon, 23 Apr 2018 12:19:44 -0000 > fairly pleased with that. Am going to try the test case that Mike Tancsa > posted to see if I can get it to lockup today though,. now that I am in > front of it to reset of required. Will report results either way... So, I have been ran the iperf scripts all day (about 4 hours now) with the Ryzen box being the reciever and another BSD box as the sender. I had re-enabled SMT on the Ryzen box out of curiosity. All worked fine until just no,w when it did lockup. But the lockup happened when I fired up VirtualBox as well on the Ryzen machine, had that doing a lot of disc activity and also did a lot of ZFS activity on the box itself. Which I find interesting, because your lockups were also happenng when VirtualBox was running were they not ? So, am going to try that again (the iperf test and simultaneous Win10 in VirtualBox), but with SMT off, to see if I can reproduce it. -pete.