From owner-freebsd-net@FreeBSD.ORG Mon Apr 11 05:49:35 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35FB11065673 for ; Mon, 11 Apr 2011 05:49:35 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id B67788FC19 for ; Mon, 11 Apr 2011 05:49:34 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.4/8.14.4) with ESMTP id p3B5nWut058945; Mon, 11 Apr 2011 09:49:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.4/8.14.4/Submit) id p3B5nWZS058944; Mon, 11 Apr 2011 09:49:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 11 Apr 2011 09:49:32 +0400 From: Gleb Smirnoff To: Przemyslaw Frasunek Message-ID: <20110411054932.GU84445@FreeBSD.org> References: <4D947756.6050808@freebsd.lublin.pl> <4D9F6C71.1040209@frasunek.com> <4DA171BA.9000507@frasunek.com> <4DA1E39C.9090300@rdtc.ru> <4DA23090.8060206@frasunek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4DA23090.8060206@frasunek.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@FreeBSD.org, Eugene Grosbein Subject: Re: mpd5/Netgraph issues after upgrading to 7.4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 05:49:35 -0000 On Mon, Apr 11, 2011 at 12:34:56AM +0200, Przemyslaw Frasunek wrote: P> > Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column. P> > If you see non-zero values there, you need to increase netgraph memory limits P> > net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf. P> P> Unfortunately, increasing net.graph.maxdata & net.graph.maxalloc didn't P> solved EPERM problems on netgraph control sockets. It is still appearing P> every few hours, but failure counters are zero: IMO, any kind of memory allocation code (malloc, uma, netgraph item allocator) never return EPERM, they return ENOMEM or ENOBUFS. So, there is a bug somewhere else. -- Totus tuus, Glebius.