From owner-freebsd-bugs@freebsd.org Sat Oct 7 19:51:55 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 A214FE40D0F for ; Sat, 7 Oct 2017 19:51:55 +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 0F17B67C66 for ; Sat, 7 Oct 2017 19:51:54 +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 v97Jpsqg009411 for ; Sat, 7 Oct 2017 19:51:54 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: Sat, 07 Oct 2017 19:51:54 +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: Sat, 07 Oct 2017 19:51:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #102 from Don Lewis --- I finally got around to contacting AMD a couple weeks ago about a warranty replacement for my CPU. My original CPU had a date code of 1708SUT and the= new one has a date code of 1733SUS. There is no evidence that the replacement = was manually tested. My first poudriere run after installing the new CPU, with all else unchanged (no clock speed changes or the BIOS upgrade requested by AMD) was much improved, but with both of the typical lang/ghc and lang/go build failures. Next, I wanted to test the LDT fixes that were committed to 12.0-CURRENT a couple days ago, so I upgraded kernel and world from r323398 to r324367. I also changed the RAM clock from the 1866 MHz override that I had been using= to the BIOS auto setting of 2400 MHz. The following poudriere run succeeded in building lang/ghc (which I've never seen happen when building my full set of ports), but lang/go still failed to build, and one of the py-* ports had a build runaway. Next I upgraded to the BIOS to AGESA 1.0.0.6b. This time, lang/go failed to build, guile segfaulted when building finance/gnucash, and devel/doxygen experienced a build runaway. Other than lang/go, I don't think any of these problems are Ryzen-specific.= I have see this gnucash build problem on my FX-8320E, but I think only when building using a 12.0-CURRENT build jail. It happens very frequently, but = not 100% of the time. I have also seen build runaway failures on my FX-8320E b= ut they seem to be pretty rare. They definitely do seem to be more common on = my Ryzen machine. --=20 You are receiving this mail because: You are the assignee for the bug.=