From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 23:53:32 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 194FA16A41F; Fri, 4 Nov 2005 23:53:32 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A728643D75; Fri, 4 Nov 2005 23:53:26 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA4NrOCm030835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 02:53:24 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA4NrI1Y030834; Sat, 5 Nov 2005 02:53:18 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 02:53:18 +0300 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20051104235318.GL91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436B9E4C.1030506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <436B9E4C.1030506@freebsd.org> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 04 Nov 2005 23:53:32 -0000 On Fri, Nov 04, 2005 at 06:45:48PM +0100, Andre Oppermann wrote: A> >This isssue is seen on 3 different PCs running recent -current, clients A> >for a FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). A> >All 3 clients have a small RAM, which may be a cause for faster apparition A> >of the issue. A> A> Hmmm... There are way too many in the packet cache (zone). Normally they A> should get free'd back into the mbuf and cluster zones if there are too A> many. A> I have to track down why UMA isn't doing that. I can easily reproduce the following situation: glebius@morannon:~:|>vmstat -z | grep mbuf mbuf_packet: 256, 0, 18446744073709526976, 24896, 68208 mbuf: 256, 0, 25026, 68, 470970 mbuf_cluster: 2048, 25280, 25280, 0, 25280 mbuf_jumbo_9k: 9216, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0 glebius@morannon:~:|>netstat -m 386/24964/25350 mbufs in use (current/cache/total) 384/24896/25280/25280 mbuf clusters in use (current/cache/total/max) 0/5/6576 sfbufs in use (current/peak/max) 864K/56033K/56897K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines In this state any cluster allocations fail. All I need to do is to download several Mb via bge(4) NIC. Backing out your changes fixes the problem. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE