From owner-freebsd-toolchain@freebsd.org Fri Jun 23 03:19:15 2017 Return-Path: Delivered-To: freebsd-toolchain@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 E103ED9B178 for ; Fri, 23 Jun 2017 03:19: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 89DD87581A for ; Fri, 23 Jun 2017 03:19: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 v5N3JF0R023740 for ; Fri, 23 Jun 2017 03:19:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Date: Fri, 23 Jun 2017 03:19:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: chrysalis@chrysalisnet.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@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-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 03:19:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220184 --- Comment #16 from Chris Collins --- I am not insisting its not hardware and I continue to persue the hardware route. I am about to go bed as is 4am here, but I upped the vcore on my cpu and dr= am voltage on the system and done 2 buildworlds since with no segfaults, it is= an old cpu so is possible voltage degradation has occurred to the point that s= tock voltage is not enough to be stable which is why I have raised the voltage. I will start another buildworld now which will be a third, if it succeeds it will be the first time 3 have worked in a row. It is still on the GENERIC kernel as well. I will also do more runs tomorrow with an empty src.conf. If these new runs all work (with increased voltage and of course also is go= od on my xeon), then yes I accept that as a hardware issue, and is possible my= old laptop may have similar issues as that is old as well. :) --=20 You are receiving this mail because: You are the assignee for the bug.=