From owner-freebsd-hackers  Fri Oct 11 00:13:06 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA24073
          for hackers-outgoing; Fri, 11 Oct 1996 00:13:06 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24064
          for <hackers@freebsd.org>; Fri, 11 Oct 1996 00:12:46 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id RAA03712; Fri, 11 Oct 1996 17:10:20 +1000 (EST)
Date: Fri, 11 Oct 1996 17:10:19 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: hackers@freebsd.org
Subject: Tracking a kmem leak
Message-ID: <Pine.BSF.3.91.961011170326.2059F-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

I have suspected leaky kernel.  The suspect code is an lkm.  The machine 
is an 8MB RAM 486 which was very happy (100 days uptime) until I started 
using the lkm.  Now, it has a hard time staying up for 24 hours.  
OS is 2.1.0R, and I don't want to say what the lkm is just at the moment, 
but I would like some pointers on how I can determine how much mem the 
kernel is occupying, so I can work out if it really is leaking.

Thanks very much,

Danny