From owner-freebsd-stable@freebsd.org  Wed Jan 31 00:37:28 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
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 A767AECC496
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 31 Jan 2018 00:37:28 +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 43FDC6A0BA;
 Wed, 31 Jan 2018 00:37:28 +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 w0V0bviu021864
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Wed, 31 Jan 2018 00:37:59 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 w0V0ReuQ007979
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Tue, 30 Jan 2018 16:37:20 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Date: Tue, 30 Jan 2018 16:37:19 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
To: Mike Tancsa <mike@sentex.net>
cc: freebsd-stable@freebsd.org, Andriy Gapon <avg@freebsd.org>,
 Peter Moody <freebsd@hda3.com>, Pete French <petefrench@ingresso.co.uk>
In-Reply-To: <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net>
Message-ID: <tkrat.3fd2dbfd38426c4e@FreeBSD.org>
References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net>
 <dd29d77a-deb9-423e-f9b8-cb07387bbfd5@sentex.net>
 <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com>
 <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net>
 <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com>
 <CAMgUhpop54hJ+iq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com>
 <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC+D9fddENPiiFng@mail.gmail.com>
 <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk>
 <tkrat.8fa97919286143d7@FreeBSD.org>
 <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net>
 <CADbMJxkRR8s1=WWXP+H9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com>
 <343acf99-3e9e-093a-7390-c142396c2985@sentex.net>
 <tkrat.975666e9f483a6a0@FreeBSD.org>
 <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net>
 <tkrat.ada77e0420783bed@FreeBSD.org>
 <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net>
 <tkrat.e541d1b83f4f6c75@FreeBSD.org>
 <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net>
 <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2018 00:37:28 -0000

On 30 Jan, Mike Tancsa wrote:
> 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

Interesting ...

> ... 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

I'd file a PR to capture all the information in one place and drop a
pointer on freebsd-current.