From owner-freebsd-bugs@freebsd.org  Mon Aug 21 18:50:51 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 468C4DEE424
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 21 Aug 2017 18:50:51 +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 34B318009E
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Aug 2017 18:50:51 +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 v7LIoorS005962
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Aug 2017 18:50:51 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, 21 Aug 2017 18:50:50 +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: markmi@dsl-only.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-hpUJuA6m3e@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, 21 Aug 2017 18:50:51 -0000

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

--- Comment #86 from Mark Millard <markmi@dsl-only.net> ---
AMD wants to RMA the CPU for the Ryzen7 1800X PC that
I (sometimes) have access to.

So once the logistics are worked out and arrangements
made I will be out of the Ryzen testing process again.

Once this starts it could be a month or so before I'd
again have access.


FYI: with 13813 built so far the only
SIGSEGV/SIGBUS types have errors under
kern.sched.steal_idle=3D0 have been the 2
/compat/linux/usr/bin/gcc related SIGSEGV's.
There have been 37 failures overall. Some
are tied to not finding files so I've no
clue if those are tied to the odd problems
with such or not. But most are tied to
source code issues. A few failed to fetch.

The FreeBSD context for these tests is:

# uname -apKU
FreeBSD FBSDx6411SL 11.1-STABLE FreeBSD 11.1-STABLE  r322596  amd64 amd64
1101501 1101501

This is as a guest in a VirtualBox virtual machine
under Windows 10 Pro. 8 "processors" assigned in
VirtualBox. Around 50 GiBytes of RAM assigned.

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