From owner-freebsd-bugs@freebsd.org  Wed Jul 26 17:37:19 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 828A9DAB6AD
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 26 Jul 2017 17:37:19 +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 7089F6E498
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 17:37:19 +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 v6QHbJAJ028707
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 17:37:19 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: Wed, 26 Jul 2017 17:37:19 +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.0-STABLE
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-ic6NqpA4QZ@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: Wed, 26 Jul 2017 17:37:19 -0000

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

--- Comment #2 from Nils Beyer <nbe@renzel.net> ---
(In reply to Don Lewis from the other ticket)

> Too bad you're not running ECC RAM, that would eliminate one potential si=
lent cause of strange behavior.

I do have ECC RAM on my second Ryzen system - that one with the 16GB RAM wh=
ich
is too low for poudriere builds. And there, I get these "unable to rename
temporary" errors while buildkernel/buildworld stress (using TMPFS), too.

For the completeness, I'm doing my stress_test buildkernel/buildworld on th=
at
system now without TMPFS. Will let you know how it goes. I guess that are no
such errors...

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