From owner-freebsd-bugs@freebsd.org Thu Aug 3 05:06: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 1CB5EDCA39A for ; Thu, 3 Aug 2017 05:06: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 0AFC666D03 for ; Thu, 3 Aug 2017 05:06: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 v7356Ea9056019 for ; Thu, 3 Aug 2017 05:06:14 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: Thu, 03 Aug 2017 05:06: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: 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: Thu, 03 Aug 2017 05:06:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #45 from Don Lewis --- I've never seen a successful amd64 ghc build. i386, no problem. I don't recall seeing that assert before, but it could have been hiding in = the weeds. It is strangely consistent, though. One difference between my buildworld/buildkernel results, which were fairly good, and my poudriere runs, which had more fallout is that the latter have= a much larger memory footprint. The machine I'm testing has 64GB of RAM, with tons free during the buildworld/buildkernel test, even with tmpfs. On the other hand, when I'm running poudriere with tmpfs, there is a lot of memory pressure and the machine starts using swap. I'm wondering if page fault exceptions sometimes get mis-reported or reported somewhat differently than older CPUs, causing us to misinterpret them has hard sigsegv faults. This = fits the Linux symptoms, especially the bash segfaults. If libtool is being use= d, then the bash process for each libtool execution will sit and wait for the compiler process that it spawed to finish. In the meantime, the memmory us= ed by bash will be idle is is likely to get paged out. After the compiler exi= ts and bash restarts, it is likely to experience a number of page faults. Now that the system hang/crash problem is fixed for me, which accounted for many of the earlier failures that I saw, and which was not sensitive to SMT= , or clock speed, I'm going to go back to some underclocking tests with SMT disa= bled to see if that has any effect when building ports. --=20 You are receiving this mail because: You are the assignee for the bug.=