From owner-freebsd-bugs@freebsd.org Mon Aug 7 23:35:15 2017 Return-Path: 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 3E6CBDD0422 for ; Mon, 7 Aug 2017 23:35:15 +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 2CF2D6385F for ; Mon, 7 Aug 2017 23:35:15 +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 v77NZFEd084877 for ; Mon, 7 Aug 2017 23:35:15 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 23:35:15 +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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 23:35:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #66 from Nils Beyer --- (In reply to Don Lewis from comment #65) > I am not convinced that the rename problem isn't a FreeBSD problem. It's= rare enough that it is difficult to track down. I wasn't able to get that "unable to rename" on my Xeon E3-1220v3. Granted, it's a 4C/4T CPU that has been tackled with 20 threads. I don't have another Non-Ryzen 8C/16T (or higher) CPU at my disposal at the moment so I cannot confirm or not confirm that this issue happens elsewhere (that would hint t= o a FreeBSD problem indeed). Maybe someone else can jump in? Would it be sensible to open a new bug report for that "unable to rename" problem? --=20 You are receiving this mail because: You are the assignee for the bug.=