Date: Thu, 5 Feb 2009 02:55:39 -0800 From: Sergey S <ad.sergey@gmail.com> To: Mikolaj Golub <to.my.trociny@gmail.com> Cc: remko@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: misc/131290: How to completely freeze FreeBSD 7.1 under a non-privileged user Message-ID: <ab09a9970902050255x328b63fcob52921f8ef98ea4@mail.gmail.com> In-Reply-To: <86iqnrb8aa.fsf@kopusha.onet> References: <200902021314.n12DEwd3098744@freefall.freebsd.org> <ab09a9970902021213h6e58a1b4o56bcfabb2e5da3e6@mail.gmail.com> <817i47oibn.fsf@zhuzha.ua1> <ab09a9970902030419j92add19y837afc7aa871aabb@mail.gmail.com> <86iqnrb8aa.fsf@kopusha.onet>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. > But I am afraid this won't help and you will have to make the system > core dump (as described at URL above) and do post-mortem analysis of the dump. Mikolaj, I've forgotten to note that my Erlang is built with --enable-smp-support option. It's significant. Please, take a look at what is going on in erlang-bugs mailing list: http://erlang.org/pipermail/erlang-bugs/2009-February/001189.html Kenji Rikitake, wrote that he's able to reproduce the bug, but only with --enable-smp-support enabled. Also he's saying that system hangs with no core dump... Anyway, I'm going to create core dump today (yesterday, I didn't see a dump in /var/crash, after reset. But I didn't use dumpon before). Please, say if you will reproduce it with --enable-smp-support option. -- Sergey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab09a9970902050255x328b63fcob52921f8ef98ea4>