From owner-freebsd-current  Fri Oct 18 14: 8:37 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 EBE9637B406; Fri, 18 Oct 2002 14:08:35 -0700 (PDT)
Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8776543EC5; Fri, 18 Oct 2002 14:08:32 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0209.cvx21-bradley.dialup.earthlink.net ([209.179.192.209] helo=mindspring.com)
	by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1)
	id 182eM9-0002ud-00; Fri, 18 Oct 2002 14:08:29 -0700
Message-ID: <3DB07805.AB4BAA15@mindspring.com>
Date: Fri, 18 Oct 2002 14:07:17 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Stuyts <ben@stuyts.nl>
Cc: current@freebsd.org, Jeff Roberson <jroberson@chesapeake.net>,
	Robert Watson <rwatson@freebsd.org>, jeff@freebsd.org,
	Alfred Perlstein <alfred@FreeBSD.ORG>
Subject: Re: [Ugly PATCH] Again: panic kmem_malloc()
References: <4.3.2.7.2.20021018125313.00bb8990@terminus>
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

Ben Stuyts wrote:
> Just had another panic, same kmem_malloc(). I did a trace but forgot to
> write the traceback down.

Wait until the next one, and remember to write it down; preferrably,
obtain a system dump image, so you can examine it with the debugger,
and make sure that the kernel you are running has a debuggable
counterpart already there (i.e. you used "config -g" to create the
kernel you are running).


> In any case, there was a semop() call in the traceback.

Not useful, without the full traceback.


> Furthermore, this might be interesting: the last vmstat -m log
> before the panic. Maybe someone can check if these values are reasonable?
> The system has 64 MB memory and has been up for about 24 hrs with almost no
> load.
>            sem344456  5390K   5390K   344456  16,1024,4096

Almost 5.3M of unswappable physical memory dedicated to semaphores
seems like a bit much.

But without knowing what software you are running, it's hard to say
if the number is unreasonable, or not.

-- Terry

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