From owner-freebsd-bugs@freebsd.org Mon Aug 7 22:22:41 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 4CBB1DCCB59 for ; Mon, 7 Aug 2017 22:22:41 +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 3AF651AC4 for ; Mon, 7 Aug 2017 22:22:41 +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 v77MMeBL011778 for ; Mon, 7 Aug 2017 22:22:41 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:22:41 +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: truckman@FreeBSD.org 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 22:22:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #63 from Don Lewis --- (In reply to Nils Beyer from comment #61) Hard to say ... If it is something triggered by context switches and is well understood, it might be possible to add some synchronization code in that path as a workaround. It might be a slow path through some logic that was missed by AMD's test procedures. My testing does seem to indicate that there could be a sensiti= vity to the core clock speed, but it doesn't seem to be a sharp edge, and it also doesn't seem to be temperature sensitive. Doing a better job of testing sh= ould catch the bad chips, at the possible expense of throwing out a lot of them.= It might be possible to work around that in microcode by allowing more time for the signals propagate. It could also be some sort of other signal integrity problem, which should = also be possible to catch in test, but would be more difficult to work around. In either of these cases, the best long term fix is a new stepping. --=20 You are receiving this mail because: You are the assignee for the bug.=