From owner-freebsd-stable@freebsd.org Mon Feb 12 21:49:54 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 E48CEF2061F for ; Mon, 12 Feb 2018 21:49:53 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 837246FC4E; Mon, 12 Feb 2018 21:49:53 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w1CLoQCX066457 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 12 Feb 2018 21:50:28 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w1CLejaW069529 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Feb 2018 13:49:40 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Mon, 12 Feb 2018 13:49:38 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Eugene Grosbein cc: Mike Tancsa , freebsd-stable@freebsd.org, Peter Moody , Andriy Gapon , Pete French In-Reply-To: <5A71C5AE.6020202@grosbein.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-5 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE 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, 12 Feb 2018 21:49:54 -0000 On 31 Jan, Eugene Grosbein wrote: > 31.01.2018 4:36, Mike Tancsa =DF=D8=E8=D5=E2: >> 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 >>=20 >>=20 >> 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 >>=20 >> ... 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 >=20 > That's really strange. Could you try to do "sysctl kern.eventtimer.period= ic=3D1" > 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=3D417183+0+archive/2018/freeb= sd-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.