From owner-freebsd-current  Wed Oct 16  1:59: 4 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9526C37B401
	for <current@freebsd.org>; Wed, 16 Oct 2002 01:59:03 -0700 (PDT)
Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2E0B543E77
	for <current@freebsd.org>; Wed, 16 Oct 2002 01:59:03 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0009.cvx21-bradley.dialup.earthlink.net ([209.179.192.9] helo=mindspring.com)
	by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 181k13-0006WQ-00; Wed, 16 Oct 2002 01:58:57 -0700
Message-ID: <3DAD2934.D0EA6C41@mindspring.com>
Date: Wed, 16 Oct 2002 01:54:12 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Makoto Matsushita <matusita@jp.FreeBSD.org>
Cc: jroberson@chesapeake.net, current@FreeBSD.ORG
Subject: Re: Kernel panic with panic: kmem_malloc(4096): kmem_map toosmall...
References: <20021015111520K.matusita@jp.FreeBSD.org>
		<20021015232745.B89360-100000@mail.chesapeake.net> <20021016171835E.matusita@jp.FreeBSD.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Makoto Matsushita wrote:
> jroberson> I suspect that there is some other bug then.  1/2 of your
> jroberson> memory should not be consumed by kernel malloc.  Do you
> jroberson> have an abnormally large MD or something?
> 
> MD devices are used to create installation floppies but no, it should
> be 1.44MB/2.88MB size, relatively small one.

The worst case failure with my "Ugly patch" should be that things hang,
and quit running completey.

If you could save a "vmstat -m" periodically, approaching the problem
this may help us identify where the memory is going, e.g. the output
from running this script:

#!/bin/sh
INTERVAL=20
while true
do
	for i in 0 1 2 3 4 5 6 7 8 9
	do
		vmstat -m > vmstatlog.$i
		sync
		sleep ${INTERVAL}
	done
done

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message