Date: Fri, 23 Jun 2017 03:19:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Message-ID: <bug-220184-29464-u8okI3QSW8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220184-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-220184-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220184 --- Comment #16 from Chris Collins <chrysalis@chrysalisnet.org> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220184-29464-u8okI3QSW8>