From owner-freebsd-bugs@FreeBSD.ORG Thu Feb 5 10:55:41 2009 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 296081065673; Thu, 5 Feb 2009 10:55:41 +0000 (UTC) (envelope-from ad.sergey@gmail.com) Received: from mail-fx0-f17.google.com (mail-fx0-f17.google.com [209.85.220.17]) by mx1.freebsd.org (Postfix) with ESMTP id 816218FC26; Thu, 5 Feb 2009 10:55:40 +0000 (UTC) (envelope-from ad.sergey@gmail.com) Received: by fxm10 with SMTP id 10so303890fxm.19 for ; Thu, 05 Feb 2009 02:55:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Sy5SN3ay6k5L0yw3Hz6emS32bj8YwaZIV3xelIFjohk=; b=eVWnArdGX7En5iZuPSEzrdIHsgZz5wr118Y2M58QUSLg/YvMAOSiDKMa7NpkzXx45C alzia3toYFIPaJiKZE7+tk5REjmDpkhFdbSkgka9IMxtEz2gJn+fCxNNe1gJIt8HTZVh QkBhijz+RqETHtCabSskE0vm58nK2sVU8vpx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=j8cfn+j455sgYp5+AdDQC4U8XbHCWFkcwknTAGml4Zg8TwqM0ppbX38vPy1gPGyJyo racnU95rMX33qSsaMOpFNP/zYlJpdRpDqinzBd+WZ6nv1r8MMpL2JT3kfED9btDXiMHu 1Q3lcKZoVghNhxGrr/yYYQyHeTWiCwwBU8Eng= MIME-Version: 1.0 Received: by 10.181.51.14 with SMTP id d14mr127584bkk.63.1233831339442; Thu, 05 Feb 2009 02:55:39 -0800 (PST) In-Reply-To: <86iqnrb8aa.fsf@kopusha.onet> References: <200902021314.n12DEwd3098744@freefall.freebsd.org> <817i47oibn.fsf@zhuzha.ua1> <86iqnrb8aa.fsf@kopusha.onet> Date: Thu, 5 Feb 2009 02:55:39 -0800 Message-ID: From: Sergey S To: Mikolaj Golub Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: remko@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: misc/131290: How to completely freeze FreeBSD 7.1 under a non-privileged user X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2009 10:55:41 -0000 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