From owner-freebsd-net@FreeBSD.ORG Mon Apr 11 07:56:29 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 7953B106564A for ; Mon, 11 Apr 2011 07:56:29 +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 F37098FC0A for ; Mon, 11 Apr 2011 07:56:28 +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 p3B7uRof059889; Mon, 11 Apr 2011 11:56:27 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.4/8.14.4/Submit) id p3B7uQpE059888; Mon, 11 Apr 2011 11:56:26 +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 11:56:26 +0400 From: Gleb Smirnoff To: Eugene Grosbein Message-ID: <20110411075626.GV84445@glebius.int.ru> References: <4D947756.6050808@freebsd.lublin.pl> <4D9F6C71.1040209@frasunek.com> <4DA171BA.9000507@frasunek.com> <4DA1E39C.9090300@rdtc.ru> <4DA23090.8060206@frasunek.com> <20110411054932.GU84445@FreeBSD.org> <4DA2A5AA.4060802@frasunek.com> <4DA2ABFA.7030108@rdtc.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4DA2ABFA.7030108@rdtc.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@FreeBSD.org, Przemyslaw Frasunek 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 07:56:29 -0000 On Mon, Apr 11, 2011 at 02:21:30PM +0700, Eugene Grosbein wrote: E> On 11.04.2011 13:54, Przemyslaw Frasunek wrote: E> >> IMO, any kind of memory allocation code (malloc, uma, netgraph item E> >> allocator) never return EPERM, they return ENOMEM or ENOBUFS. E> >> E> >> So, there is a bug somewhere else. E> > E> > I think so, but for me it still looks like resource shortage. As I wrote E> > before, when EPERM starts appearing, I'm unable to run "ngctl list". E> E> Increase sysctl kern.ipc.maxsockbuf. E> I was forced to rise it upto 80MB (sic!) as 8MB was not enough to me. Ah, I found where EPERM comes from. Will fix it soon. -- Totus tuus, Glebius.