From owner-freebsd-i386@FreeBSD.ORG Wed Sep 27 03:50:18 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D47716A403 for ; Wed, 27 Sep 2006 03:50:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BB343D49 for ; Wed, 27 Sep 2006 03:50:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8R3oFLK026850 for ; Wed, 27 Sep 2006 03:50:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8R3oF9i026849; Wed, 27 Sep 2006 03:50:15 GMT (envelope-from gnats) Date: Wed, 27 Sep 2006 03:50:15 GMT Message-Id: <200609270350.k8R3oF9i026849@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Igor Soumenkov" <2igosha@gmail.com> Cc: Subject: Re: i386/103664: kmem_map_too_small panic after about 7d uptime on 6.1-release X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Igor Soumenkov <2igosha@gmail.com> List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 03:50:18 -0000 The following reply was made to PR i386/103664; it has been noted by GNATS. From: "Igor Soumenkov" <2igosha@gmail.com> To: "Ed Maste" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: i386/103664: kmem_map_too_small panic after about 7d uptime on 6.1-release Date: Wed, 27 Sep 2006 07:42:46 +0400 I found out that it was ipfw that caused the memory leak and lead to the panic. And I found the fix in version 1.141 of file ip_fw2.c 3944,3945c3944 < rule = layer3_chain.reap; < layer3_chain.reap = NULL; --- > rule = layer3_chain.reap, layer3_chain.reap = NULL; 3947c3946 < if (rule != NULL) --- > if (layer3_chain.reap != NULL) Seems that there are no leaks now. +Warning: memory type IpFw/IpAcct leaked memory on destroy (108606 allocations, 6993216 bytes leaked). On 9/27/06, Ed Maste wrote: > > I am running 6.1-RELEASE on a two-xeon machine with 2GB ram, acpi and HT disabled. The system is running the SMP kernel and each week it panics with "kmem_map too small" error. > > You can have a look at vmstat -m output over time, to see if one > particular allocation type is constantly growing. If that's the > case it might suggest the location of a leak. You can also run > vmstat -m on a core file to examine the malloc statistics. > -- Igor Soumenkov.