From owner-freebsd-net@FreeBSD.ORG Tue Feb 16 17:23:25 2010 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 8CAD6106566B; Tue, 16 Feb 2010 17:23:25 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 52D5D8FC1F; Tue, 16 Feb 2010 17:23:24 +0000 (UTC) Received: from [192.168.1.38] ([70.71.167.197]) (authenticated bits=0) by sippysoft.com (8.14.3/8.14.3) with ESMTP id o1GHNHcl022112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Feb 2010 09:23:21 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <4B7AD495.30900@FreeBSD.org> Date: Tue, 16 Feb 2010 09:23:33 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <4B79297D.9080403@FreeBSD.org> <4B79205B.619A0A1A@verizon.net> <4B7A38F5.3090404@FreeBSD.org> <4B7A7D2C.9040200@quip.cz> In-Reply-To: <4B7A7D2C.9040200@quip.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alfred Perlstein , freebsd-net@FreeBSD.org, Sergey Babkin , "David G. Lawrence" , Jack Vogel Subject: Re: Sudden mbuf demand increase and shortage under the load 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: Tue, 16 Feb 2010 17:23:25 -0000 Miroslav Lachman wrote: > Can it be related to this issue somehow? > > http://lists.freebsd.org/pipermail/freebsd-current/2009-August/011013.html > http://lists.freebsd.org/pipermail/freebsd-current/2009-August/010740.html > > It was tested on FreeBSD 8 and high UDP traffic on igb interfaces emits > messages "GET BUF: dmamap load failure - 12" and later results in kernel > panic. > We have not received any response to this report. Could be the issue, however in our case there is no panic, just that all userland activity in the system ceases for 2 minutes after it reaches certain network load level. -Maxim