Date: Fri, 11 Oct 1996 18:48:36 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: danny@panda.hilink.com.au (Daniel O'Callaghan) Cc: hackers@FreeBSD.ORG Subject: Re: Tracking a kmem leak Message-ID: <199610110918.SAA25444@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.BSF.3.91.961011170326.2059F-100000@panda.hilink.com.au> from "Daniel O'Callaghan" at Oct 11, 96 05:10:19 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Callaghan stands accused of saying: > > 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. 'vmstat -m' is your friend. Note that if you're talking about the Linux emulator, several leaks are fixed in -current but not before (curses 8( ) > Danny -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610110918.SAA25444>