From owner-freebsd-stable@FreeBSD.ORG  Fri Nov 16 08:05:24 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A1AC816A417
	for <freebsd-stable@freebsd.org>; Fri, 16 Nov 2007 08:05:24 +0000 (UTC)
	(envelope-from andrew@rinet.ru)
Received: from mail.tsscom.ru (mail.tsscom.ru [195.10.205.29])
	by mx1.freebsd.org (Postfix) with ESMTP id 963F213C45B
	for <freebsd-stable@freebsd.org>; Fri, 16 Nov 2007 08:05:22 +0000 (UTC)
	(envelope-from andrew@rinet.ru)
Received: from [195.10.205.145] (HELO [10.10.80.29])
	by mail.tsscom.ru (CommuniGate Pro SMTP 5.1.8)
	with ESMTP id 241086 for freebsd-stable@freebsd.org;
	Fri, 16 Nov 2007 11:05:12 +0300
From: Andrew Kolchoogin <andrew@rinet.ru>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
Organization: Cronyx Plus LLC
Date: Fri, 16 Nov 2007 11:05:05 +0300
Message-Id: <1195200305.3532.10.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1.1 
Content-Transfer-Encoding: quoted-printable
Subject: kmem_map too small
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2007 08:05:24 -0000

Dear colleagues,

    do you have any suggestions about how I should trace what condition
generates kernel panic with reason "kmem_map too small"?

    Operating system is FreeBSD 6.2-p8, no unusual software runs on this
machine -- it runs Asterisk with dummy Zapata driver, FreeRADIUS v1.1.7,
MySQL v5.0 with single database for FreeRADIUS, Apache v1.3 for DialUp
Admin. Sure, sshd, ntpd, syslogd. :)

    When this machine has run FreeBSD 5.4, no such problems were exist
-- uptime was about 250 days.

--=20
    =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
        =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9A=D0=BE=D0=BB=D1=8C=D1=87=
=D1=83=D0=B3=D0=B8=D0=BD.