Date: Thu, 26 Oct 2006 09:14:56 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Scott Long <scottl@samsco.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Andreas Sons <sons@zs64.net>, Stefan Bethke <stb@lassitu.de> Subject: Re: panic: kmem_map too small Message-ID: <20061026091253.J69980@fledge.watson.org> In-Reply-To: <45400286.9020402@samsco.org> References: <CD619308-6B7B-4B68-B011-CE979D67E0C1@lassitu.de> <20061025183308.L33725@fledge.watson.org> <838FCA83-20F8-4A09-A025-E69956032F86@lassitu.de> <45400286.9020402@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Oct 2006, Scott Long wrote: > There are no obvious culprits from what you posted. The kernel was only > trying to allocate 60 bytes, and the 64-byte bucket didn't look to be overly > used. None of the other zones look terribly over-used either. The 'show > malloc' command doesn't really give enough stats to be terribly useful, > IMHO. What would you add to the output to make it more useful? The main difference between "show malloc" and "vmstat -m", other than any "use over time" associated with multiple runs of vmstat -m, is the malloc size bitmask. This is relatively easily added to kern_malloc.c. > And neither of the commands can effectively track things like contig memory > allocator. Can you try the following two commands: Want to add "show contigmalloc"? I've found it significantly easier to debug memory leaks since adding these DDB commands, but they are easily enhanced to carry more information than they do now. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061026091253.J69980>