From owner-freebsd-stable@FreeBSD.ORG  Sun Oct 23 07:43:44 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B333016A41F
	for <freebsd-stable@freebsd.org>; Sun, 23 Oct 2005 07:43:44 +0000 (GMT)
	(envelope-from for.bounces@dun.ukr.net)
Received: from dun.ukr.net (dun.ukr.net [212.42.67.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5953943D45
	for <freebsd-stable@freebsd.org>; Sun, 23 Oct 2005 07:43:44 +0000 (GMT)
	(envelope-from for.bounces@dun.ukr.net)
Received: from sharun by dun.ukr.net with local ID 1ETaW6-000PGo-S9
	for freebsd-stable@freebsd.org; Sun, 23 Oct 2005 10:43:42 +0300
Date: Sun, 23 Oct 2005 10:43:42 +0300
From: Vladimir Sharun <sharun@ukr.net>
To: freebsd-stable@freebsd.org
Message-ID: <20051023074342.GA97095@dun.ukr.net>
Mail-Followup-To: Vladimir Sharun <sharun@ukr.net>, freebsd-stable@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Subject: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
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: Sun, 23 Oct 2005 07:43:44 -0000

We have 2xOpteron/2Gb RAM server with extrensive disk load. Every week or two
it suddenly hangs with "kmem_malloc(4096): kmem_map too small 335bla-bla allocated". 
I look onto handbook and put vm.kmem_size_max="536870912" onto /boot/loader.conf.
Today was the same with the new parameters. Is there any other solutions ?

# sysctl -a | grep kmem
vm.kmem_size: 536870912
vm.kmem_size_max: 536870912
vm.kmem_size_scale: 3

The only vm.kmem_size_max on loader.conf, no vm.kmem_size.

We're running FreeBSD 6.0-BETA5 #0: Wed Sep 28 16:54:33 EEST 2005
in i386 mode. The same was with 5.3/5.4 and NetBSD 2.0 on this machine.