From owner-freebsd-bugs@freebsd.org Sun Aug 20 08:55:08 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 894D7DE83DC for ; Sun, 20 Aug 2017 08:55:08 +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 779C07DA37 for ; Sun, 20 Aug 2017 08:55:08 +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 v7K8t8OC047170 for ; Sun, 20 Aug 2017 08:55:08 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: Sun, 20 Aug 2017 08:55:08 +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: 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: Sun, 20 Aug 2017 08:55:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #81 from Mark Millard --- (In reply to Don Lewis from comment #80) FYI for my tests: So far with kern.sched.steal_idle=3D0 I've never had lang/ghc fail to build. So far with kern.sched.steal_idle=3D1 I've always had lang/ghc fail to build --before it even started using ghc-stage1. (I monitored via top.) These failures do seem random for at what point of the lang/ghc build hat the failure happens. (Builds that work take vastly longer to complete as well.) I've done a half dozen build attempts or so each way over those two alternatives (so far). lang/ghc builds failed for kern.sched.steal_idle=3D1 every time that I've tried it, even when poudriere was configured to avoid parallel builds (including and avoiding ALLOW_MAKE_JOBS) and lang/ghc was the only thing being built, prerequisites already in place. System-wide memory bandwidth usage being high does not seem to be important to having the lang/ghc builds fail. Most of the failure examples are for CPU temperatures under 40 DegC. Only for hot days in contexts without air conditioning have I seen as high as 44 DegC for the Ryzen PC. (Liquid cooled, two 360 mm radiators, ten 120 mm fans, low end graphics card, and so on: all biased to keeping temperatures down.) Die temperature does not seem to be important to having the lang/ghc builds fail. (It is too preliminary to depend on yet but so far the kern.sched.steal_idle=3D0 "poudriere bulk -a" has had no SIGSEGV or SIGBUS like failures for any ports, unlike when I'd tried with kern.sched.steal_idle=3D1 .) I do not expect the kern.sched.steal_idle=3D0 results to be luck at this point (up to any kern.sched.balance=3D1 contribution if involved). --=20 You are receiving this mail because: You are the assignee for the bug.=