From owner-freebsd-stable@freebsd.org Fri Apr 20 11:55:29 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 EAF32F96F36 for ; Fri, 20 Apr 2018 11:55:28 +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 2EF0E7B3AF; Fri, 20 Apr 2018 11:55:28 +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 1f9UdR-000Cum-Uu; Fri, 20 Apr 2018 11:55:25 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Nimrod Levy Cc: eric@vangyzen.net, freebsd@hda3.com, truckman@freebsd.org, freebsd-stable@freebsd.org, avg@freebsd.org References: From: Pete French Message-ID: <70328375-165e-6ba4-8c21-03acd6ae8933@ingresso.co.uk> Date: Fri, 20 Apr 2018 12:55:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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: Fri, 20 Apr 2018 11:55:29 -0000 On 20/04/2018 12:48, Nimrod Levy wrote: > I'm really glad to see that I'm not the only one still interested in > this thread.  I don't really have anything new to contribute. I've been > getting about a week or so uptime out of my box. My habit has been to > see if it hangs, then reboot and rebuild latest stable and reboot and > run that for a while. Although now that this thread pops back up, I just > realized it's been 2 weeks since the last cycle. I don't trust it yet, > but I've seen clear improvement since this started. What setting sdo you have - just the ones I listed or some in the BSD setup itself ? I am surprised that the operson who said they were getting an actual Epyc server hasn't commented again on the thread. Hopefully that means it works fine on the server hardware :-) I have seen a few commits go through in STABLE related to VM which interest me, and which might cause hangs, so we shall see how it goes. Possibly looking at the Ryzen issue has flushed out a few VM problems anyway, which would be good, as more stbaility is always good (and I have a vague hope it might fix the mysetrious Go hangs too). -pete.