From owner-freebsd-net@FreeBSD.ORG  Mon Jun 18 04:47:29 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6B5841065677
	for <freebsd-net@freebsd.org>; Mon, 18 Jun 2012 04:47:29 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5])
	by mx1.freebsd.org (Postfix) with ESMTP id BF4848FC08
	for <freebsd-net@freebsd.org>; Mon, 18 Jun 2012 04:47:28 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id q5I4lKCL038227;
	Mon, 18 Jun 2012 11:47:20 +0700 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4FDEB2D8.40007@rdtc.ru>
Date: Mon, 18 Jun 2012 11:47:20 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: Arnaud Lacombe <lacombar@gmail.com>
References: <4DAD3824.7000500@frasunek.com>	<20110419074056.GG34767@glebius.int.ru>	<4DB47CE1.8@frasunek.com>	<4DB487D2.7030104@rdtc.ru>	<4DB48B76.8050101@frasunek.com>	<4DB49109.3050002@frasunek.com>	<20110425050548.GF34767@glebius.int.ru>	<4DBBBAD8.2000705@frasunek.com>	<20110513162311.GK95084@glebius.int.ru>	<4DD298AD.2060905@frasunek.com>	<20110517184613.GN74366@glebius.int.ru>	<4FDB1D71.6050908@freebsd.lublin.pl>	<4FDB2180.4030609@rdtc.ru>
	<CACqU3MW542ZvwMTOssfA7RE4o3jLT9ajD3oUAQWHo=xH0=wcoQ@mail.gmail.com>
In-Reply-To: <CACqU3MW542ZvwMTOssfA7RE4o3jLT9ajD3oUAQWHo=xH0=wcoQ@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Cc: Przemyslaw Frasunek <venglin@freebsd.lublin.pl>,
	Andriy Gapon <avg@icyb.net.ua>, freebsd-net@freebsd.org
Subject: Re: mpd5/Netgraph issues after upgrading to 7.4
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 04:47:29 -0000

17.06.2012 01:13, Arnaud Lacombe пишет:
> Hi,
> 
> On Fri, Jun 15, 2012 at 7:50 AM, Eugene Grosbein <egrosbein@rdtc.ru> wrote:
>> 15.06.2012 18:33, Przemyslaw Frasunek пишет:
>>> Dear All,
>>>
>>> unfortunately, one of my mpd5 PPPoE access servers started panicing every few
>>> hours.
>>>
>>> I'm running recent 8.3-STABLE (as of 23th May) with WITNESS, INVARIANTS and
>>> DEBUG_MEMGUARD compiled. Unfortunately, I'm unable to catch crashdump. For some
>>> reason, it is not saved on dumpdev.
>>
>> The reason is that 8-STABLE fails to stop scheduler on panic
>> that breaks writing of crashdumps.
>>
>> 8.3-STABLE has new sysctl kern.stop_scheduler_on_panic.
>> You should set it to 1 to get crashdumps saved.
>>
> Is there technical reason to have the scheduler still running after panic() ?

It seems no. That's just "a misfeature".

Eugene Grosbein