Re: SIGSEGV crash on SMP Xeon E5, can't build from ports
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 be? I'm at my wits end, all I can think of now is > to run mono in a bhyve VM to get around this, which makes me a bit sad... Looking at the backtrace from #211367, the segfault comes from mono_gchandle_free(). The default Garbage Collector (GC) beeing sgen, trying to switch to boehm may confirm that this is related to a race condition in the garbage collection? mcs has a `--gc=[sgen,boehm]` option to test this quickly, but it should be possible to tell `./configure` to disable sgen support. Sorry to not be able to provide more than this: with 4 cores, I can't remember being hit by this problem. Romain -- Romain Tartière http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) signature.asc Description: PGP signature
OPT Consultant looking for Job Skills: Java, Python, C C++
Hi , We have an OPT consultant with the following skills available, please let me know, if you have any project for her. Resume attached. TECHNICAL SKILLS Programming Languages : Java, Python, C, C++ Web Development : HTML, CSS3, XML, PHP, JSON IDE : Eclipse, Android Studio, Dev C++, Matlab, Keil Database Development : MYSQL SIEM TOOLS: Tableau, Hbase, Hive, Splunk, Spark If you need more information, please send me an email, I will get back to you with the details. Waiting to hearing back from you. Thanks and Regards, Naresh Agrawal (856) 520-3450 (856) 772-9349 Fax j...@viprosystems.com Vipro Systems LLC P Save trees. Print Only When Necessary We respect your online privacy. This is not an unsolicited mail. Under Bills.1618 Title III passed by the 105th US Congress this mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. If you are not interested in receiving our e-mails then please reply with "REMOVE" in the subject line and your Email ID (m...@freebsd.org). Will be removed from our mailing list. We are sorry for the inconvenience caused to you ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 211367] lang/mono net-p2p/sonarr Sonarr crashes on startup with SIGSEGV since base r296727 on 10.3-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211367 --- Comment #28 from Phil --- 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 cpu count or cpu type (in the VM) has no impact. Seems like something's off when there's too much memory available... Any thoughts? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: SIGSEGV crash on SMP Xeon E5, can't build from ports
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 cpu count or cpu type (in the VM) has no impact. Seems like something's off when there's too much memory available... Any thoughts? On Mon, Jan 23, 2017 at 8:50 PM Philipp Michel wrote: > 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: > > = > Got a SIGSEGV while executing native code. This usually indicates > a fatal error in the mono runtime or one of the native libraries > used by your application. > = > > I've tried to build mono from ports using the debug symbols but even the > build process fails when it tries to call mcs resulting in the same SIGSEGV > crash. I'm attaching the output below. > > 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 be? I'm at my wits end, all I can think of now is > to run mono in a bhyve VM to get around this, which makes me a bit sad... > > Thanks so much in advance for your help! > > -Phil > > > -- > echo '#! /bin/sh' > _tmpinst/bin/ilasm ; \ > r=`pwd`; m=`cd /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs > && pwd`; \ > echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/ilasm/ilasm.exe"'" "$@"' >> > _tmpinst/bin/ilasm ; \ > chmod +x _tmpinst/bin/ilasm > echo '#! /bin/sh' > _tmpinst/bin/mcs ; \ > r=`pwd`; m=`cd /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs > && pwd`; \ > echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe"'" > "$@"' >> _tmpinst/bin/mcs ; \ > chmod +x _tmpinst/bin/mcs > echo '#! /bin/sh' > _tmpinst/bin/al ; \ > r=`pwd`; m=`cd /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs > && pwd`; \ > echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_4_x/al.exe"'" > "$@"' >> _tmpinst/bin/al ; \ > chmod +x _tmpinst/bin/al > if test -w /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs; > then :; else chmod -R +w > /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs; fi > cd /var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/mcs && gmake > --no-print-directory -s NO_DIR_CHECK=1 > PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14 ' > CC='cc' all-profiles > mkdir -p -- build/deps > gmake[7]: mcs: Command not found > gmake[7]: *** [build/profiles/basic.make:93: > build/deps/basic-profile-check.exe] Error 127 > *** The compiler 'mcs' doesn't appear to be usable. > *** Trying the 'monolite' directory. > > = > Got a SIGSEGV while executing native code. This usually indicates > a fatal error in the mono runtime or one of the native libraries > used by your application. > = > > gmake[9]: *** [build/profiles/basic.make:93: > build/deps/basic-profile-check.exe] Abort trap (core dumped) > *** The contents of your 'monolite' directory may be out-of-date > *** You may want to try 'make get-monolite-latest' > gmake[9]: *** [build/profiles/basic.make:80: do-profile-check-monolite] > Error 1 > gmake[8]: *** [build/profiles/basic.make:60: do-profile-check] Error 2 > gmake[7]: *** [build/profiles/basic.make:88: do-profile-check-monolite] > Error 2 > gmake[6]: *** [build/profiles/basic.make:60: do-profile-check] Error 2 > gmake[5]: *** [Makefile:49: profile-do--basic--all] Error 2 > gmake[4]: *** [Makefile:45: profiles-do--all] Error 2 > gmake[3]: *** [Makefile:543: all-local] Error 2 > gmake[3]: Leaving directory > '/var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2/runtime' > gmake[2]: *** [Makefile:512: all-recursive] Error 1 > gmake[2]: Leaving directory > '/var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2' > gmake[1]: *** [Makefile:441: all] Error 2 > gmake[1]: Leaving directory > '/var/ports/basejail/usr/ports/lang/mono/work/mono-4.6.2' > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > > - > ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
