From owner-freebsd-stable@freebsd.org Fri Apr 20 13:39:51 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 A5550FA471B for ; Fri, 20 Apr 2018 13:39:51 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2089C746B5; Fri, 20 Apr 2018 13:39:51 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w3KDdnwL070376 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 20 Apr 2018 09:39:50 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w3KDcVqi033559; Fri, 20 Apr 2018 09:38:31 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Nimrod Levy , Pete French Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, avg@freebsd.org, freebsd@hda3.com References: <70328375-165e-6ba4-8c21-03acd6ae8933@ingresso.co.uk> From: Mike Tancsa Openpgp: preference=signencrypt Organization: Sentex Communications Message-ID: Date: Fri, 20 Apr 2018 09:38:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 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 13:39:51 -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 :( Here is a test case. https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088433.html Peter was able to recreate it as well. https://lists.freebsd.org/pipermail/freebsd-virtualization/2018-March/006187.html I dont think its VM / virtualization per se. I think Peter mentioned something about IPIs ---Mike On 4/20/2018 8:39 AM, Nimrod Levy wrote: > To be honest, I can't remember for certain what's set in the BIOS right > now. The last post I made was from 3/17 and it says I have the memory clock > lowered and c-states disabled. I don't think I've changed anything but the > build of stable since then. > > -- > Nimrod > > On Fri, Apr 20, 2018 at 7:55 AM Pete French > wrote: > >> >> >> 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. >> -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada