Date: Sun, 25 Jun 2017 21:13:58 +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-HGwODimLHD@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 #18 from Chris Collins <chrysalis@chrysalisnet.org> --- Ok a further update. After a reboot, the i5 750 machine started getting segfaults again, a few reboots later I have discovered the behaviour is fairly consistent, where a rolld o the dice occurs on a reboot, usually if the first buildworld has no problem I can probably do 3+ in a row with no segfault, but if the first ha= s a segfault then I will struggle to get just one successful buildworld. I discovered the LAPIC timer on my laptop is broken, aided by a warning on = the console, when I switched it to i8254 the problem stopped. I then fresh installed 11.0 again and discovered on 11.0 it uses i8254 by default but on 11-STABLE it uses LAPIC, when LAPIC is used I see some other odd behaviours e.g. systat -v 1 will update really slowly. I then checked on my i5 750 on 11.0 it uses LAPIC by default and seems to w= ork ok, on 11-STABLE LAPIC has the same issues as the laptop and it defaults to HPET. At the time of this post I havent tried a buildworld using a non def= ault timer, but I am running buildworld now using i8254 on the i5 750 to see what results I get, I will run many times over multiple reboots. The VMWare hypervisor has no segfault problems and uses LAPIC by default working fine on 11.0 and 11-STABLE. All the current tests are with empty src.conf aside from 'LOADER_ZFS_SUPPORT=3DYES'' and no CPUTYPE defined to try and simplify the diagnosis. --=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-HGwODimLHD>