From owner-freebsd-stable@freebsd.org Tue Feb 13 01:49:02 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 46CF9F10899 for ; Tue, 13 Feb 2018 01:49:02 +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 5EAB57B6E2; Tue, 13 Feb 2018 01:49:00 +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 w1D1mxPo076676 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 12 Feb 2018 20:48:59 -0500 (EST) (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 w1D1mtJE024807; Mon, 12 Feb 2018 20:48:55 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Don Lewis , Eugene Grosbein Cc: freebsd-stable@freebsd.org, Peter Moody , Andriy Gapon , Pete French References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <5A71C5AE.6020202@grosbein.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <73f83421-97ed-88f8-08be-39cf5a70ed20@sentex.net> Date: Mon, 12 Feb 2018 20:48:56 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-8859-5 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: Tue, 13 Feb 2018 01:49:02 -0000 On 2/12/2018 4:49 PM, Don Lewis wrote: > On 31 Jan, Eugene Grosbein wrote: >> 31.01.2018 4:36, Mike Tancsa пишет: >>> On 1/30/2018 2:51 PM, Mike Tancsa wrote: >>>> >>>> And sadly, I am still able to hang the compile in about the same place. >>>> However, if I set >>> >>> >>> OK, here is a sort of work around. If I have the box a little more busy, >>> I can avoid whatever deadlock is going on. In another console I have >>> cat /dev/urandom | sha256 >>> running while the build runs >>> >>> ... and I can compile net/samba47 from scratch without the compile >>> hanging. This problem also happens on HEAD from today. Should I start >>> a new thread on freebsd-current ? Or just file a bug report ? >>> The compile worked 4/4 >> >> That's really strange. Could you try to do "sysctl kern.eventtimer.periodic=1" >> and re-do the test without extra load? > > I'm having really good luck with the kernel patch attached to this > message: > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=417183+0+archive/2018/freebsd-hackers/20180211.freebsd-hackers > > Since applying that patch, I did three poudriere runs to build the set > of ~1700 ports that I use. Other than one gmake-related build runaway > that I've also seen on my AMD FX-8320E, I didn't see any random port > build failures. When I was last did some testing a few weeks ago, > lang/go would almost always fail. I also would seem random build > failures in lang/guile or finance/gnucash (which uses guile during its > build) on both my Ryzen and FX-8320E machines, but those built cleanly > all three times. > > I even built samba 16 times in a row without a hang. > Cool! I will give it a try! In other news, the latest BIOS patch from ASUS for my motherboard *seems* to have fixed the random hangs. In the BIOS, I had to dial down the memory one notch, disable q-states and disable core boost for my non X Ryzen CPUs. I did that Friday, and running a load that would typically lock up the box, survived the weekend. Same with the box I have in Zoo. No random freeze ups. I was also able to take the amdtemp and amdsmn code from HEAD and compile it on STABLE to confirm the CPU is / was not overheating. Peak temp in the low 50s even with the CPU cores are all maxed out. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada