From owner-freebsd-stable@freebsd.org Wed Jan 31 13:38:38 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 563F3ECBB1B for ; Wed, 31 Jan 2018 13:38:38 +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 836C383FAA; Wed, 31 Jan 2018 13:38:36 +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 w0VDcZZp007871 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 31 Jan 2018 08:38:36 -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 w0VDcYiS014106; Wed, 31 Jan 2018 08:38:34 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Eugene Grosbein , Don Lewis Cc: freebsd-stable@freebsd.org, Pete French 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: <83cc86a3-e8f9-14e4-14fd-05133417f135@sentex.net> Date: Wed, 31 Jan 2018 08:38:34 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <5A71C5AE.6020202@grosbein.net> 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: Wed, 31 Jan 2018 13:38:38 -0000 On 1/31/2018 8:33 AM, 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? Thanks for the suggestion! I actually upgraded the box to HEAD last night and will try there since the problem is there too. I just created a bug report and started a thread in freebsd-current and will follow up there with your test. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada