From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 16:48:45 2004 Return-Path: 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 947A916A4CE; Sat, 10 Jul 2004 16:48:45 +0000 (GMT) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id C725343D31; Sat, 10 Jul 2004 16:48:44 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from laptop (81-178-100-243.dsl.pipex.com [81.178.100.243]) by pengo.systems.pipex.net (Postfix) with SMTP id D98764C00205; Sat, 10 Jul 2004 17:48:42 +0100 (BST) Message-ID: <001201c4669d$bfa13bd0$f800000a@laptop> From: "Markie" To: "Brian Fundakowski Feldman" , References: <000b01c46617$1f3ba4e0$f800000a@laptop> <20040710143658.GH1626@green.homeunix.org> Date: Sat, 10 Jul 2004 17:48:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: quick interactivity? question regarding -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 16:48:45 -0000 ----- Original Message ----- From: "Brian Fundakowski Feldman" To: "Markie" Cc: Sent: Saturday, July 10, 2004 3:36 PM Subject: Re: quick interactivity? question regarding -current | On Sat, Jul 10, 2004 at 01:44:51AM +0100, Markie wrote: | > Hello, | > | > I updated my 'do-it-all' home server box from 5.2.1-R to -CURRENT the other | > day, as suggested by someone a month ago because I was having panics along | > the lines of "kmem_malloc(4096): kmem_map too small". Now, I can't | > immediately tell if this upgrade has solved my problem as the first one | > appeared after 50 days of uptime (ish) and the one that happened the other | > day (same panic) occured after only around 20 days, this is when I decided | > to go for the installkernel/world. | | Did you try seeing where all the memory went? I reimplemented KVM support | in vmstat -m for -CURRENT, so it should be more useful for that if you get | a core dump (admittedly, a rare thing ...). I didn't know about vmstat -m until the other day, I read something about `vmstat -m | grep cred` should be really low, under 100k or something (which mine is) I have no idea what KVM is in terms of kernel stuff :-) What should I be looking for, just any entry with a high mem usage? Should I setup a cron job to dump the results to a file each day so incase I do still get the panic i'll be able to look at the results atleast from the day before, maybe that would help me determine what was up if it's due to a memory leak? At the moment the most memory seems to be in 'routetbl' - 6456k in the HighUse and 1793k MemUse. All the rest are pretty much below 100k. Thanks! Markie | | -- | Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ | <> green@FreeBSD.org \ The Power to Serve! \ | Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\