From owner-freebsd-bugs@freebsd.org Wed Aug 23 06:40:07 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 4740CDDFBD6 for ; Wed, 23 Aug 2017 06:40:07 +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 3532964560 for ; Wed, 23 Aug 2017 06:40:07 +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 v7N6e6RR005449 for ; Wed, 23 Aug 2017 06:40:07 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, 23 Aug 2017 06:40:07 +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: Wed, 23 Aug 2017 06:40:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #94 from Don Lewis --- In my latest experiment, I still restricted the steal_idle to the CCX of the current SMT thread. At the CCX level, I changed thresh back to 1, but I al= so excluded the current core so that stealing from the other SMT thread can on= ly happen if the steal_thresh condition was met for it on the first pass. I s= till a fair amount of build fallout. In addition to the usual ghc SIGBUS, I also saw a couple of clang SIGABRT failures when building security/nss and www/webkit2-gtk3. Also lang/go failed with these errors: fatal error: runtime\xc2\xb7lock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count [snip] fatal: morestack on g0 SIGTRAP: trace trap PC=3D0x44ef02 m=3D1 sigcode=3D1 --=20 You are receiving this mail because: You are the assignee for the bug.=