Re: SIGSEGV crash on SMP Xeon E5, can't build from ports

2017-01-24 Thread Philipp Michel
After some more playing around trying to run mono both on bare metal and a VM, I've narrowed it down to what seems to be a memory issue. I have 256G of ram in the server. If I restrict hw.physmem=140G, mono works fine. Anything above hw.physmem=150G or so seems to cause it to crash! Changing the

Re: SIGSEGV crash on SMP Xeon E5, can't build from ports

2017-01-24 Thread Romain Tartière
On Tue, Jan 24, 2017 at 04:50:58AM +, Philipp Michel wrote: > I think it is related to this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211367 > > There are reports of several people still having this issue, seemingly all > on multiprocessor machines. > > Any idea what this could

SIGSEGV crash on SMP Xeon E5, can't build from ports

2017-01-23 Thread Philipp Michel
Hi there, I've been a longtime user of mono on FreeBSD without issues. I usually just install the pkg. I recently upgraded my machine from a Haswell E3 to a dual-socket Sandy Bridge E5 and now mono instantly crashes with the SIGSEGV error: ===