From owner-freebsd-bugs@freebsd.org  Mon Aug  7 22:42:40 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7811BDCDAA6
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  7 Aug 2017 22:42:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 665BF2769
 for <freebsd-bugs@FreeBSD.org>; Mon,  7 Aug 2017 22:42:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v77Mgenm008890
 for <freebsd-bugs@FreeBSD.org>; Mon, 7 Aug 2017 22:42:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere
 or plain buildkernel/buildworld
Date: Mon, 07 Aug 2017 22:42:40 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: nbe@renzel.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221029-8-0PwXI6ZuEX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221029-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-221029-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2017 22:42:40 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029

--- Comment #64 from Nils Beyer <nbe@renzel.net> ---
(In reply to Don Lewis from comment #63)

hmm - doesn't sound so good; if you say that there's nothing that FreeBSD c=
an
do to workaround/circumvent/mitigate the issue and that there's need for new
silicon, then I would close that bug as it isn't fixable at the moment.

The following post (just appeared):

    https://community.amd.com/message/2816419#comment-2816419

where a friendly guy tried both the "ryzen_stress_test.sh"
buildworld/buildkernel and your "ryzen_provoke_crash" program from the other
bug report - seems to support my assumption as he does not seem to get any
"unable to rename" errors in that buildworld/buildkernel test within 14 hou=
rs
(could be, of course, too short, but promising).

So, if you're okay, then I close that bug hereby...

--=20
You are receiving this mail because:
You are the assignee for the bug.=