From owner-freebsd-stable@FreeBSD.ORG Tue Sep 7 22:02:30 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 113241065696 for ; Tue, 7 Sep 2010 22:02:30 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 966EA8FC0A for ; Tue, 7 Sep 2010 22:02:29 +0000 (UTC) Received: by fxm4 with SMTP id 4so3935021fxm.13 for ; Tue, 07 Sep 2010 15:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=FeqBY+z2YfsDc9+j/wJ5Q8aWYhGPxNnMoKIQoVCbBiU=; b=YgzrA392DMi7e9FX/U0u3ddkRGGY18jNuH4cgIIyx2mSk8k5QbKjUHOJ9rHgiTNNOz u1wzQi2JAJMof9L4VQ51Ch0EW1wfbpVdVzdXIQhJ9QrPkMTjpQLqcCrpg7j9J8zOFMXq 0nS1TPH8PHW4gnAUOtp2XqcY0olWAK1wPd/Vw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=QcAFjcERoUGkbbznnBZcQ4P6O3VU6vQW9qtLWLZUlJHtCUwywIE/4rz+DfESk+ZY9P X2mlN8BvFrn1sTYl00X3HqSqglqEIArBy0uMrRpObuXepV8G2k6mkwukZiZLuZqNR75T Euinm9JNZDiPtSLpRbEy6bPxW50CMKniERSqU= MIME-Version: 1.0 Received: by 10.223.119.70 with SMTP id y6mr233217faq.65.1283896946734; Tue, 07 Sep 2010 15:02:26 -0700 (PDT) Received: by 10.223.57.20 with HTTP; Tue, 7 Sep 2010 15:02:26 -0700 (PDT) In-Reply-To: <20100907210813.GI49065@martini.nu> References: <20100907210813.GI49065@martini.nu> Date: Tue, 7 Sep 2010 17:02:26 -0500 Message-ID: From: Adam Vande More To: "Mahlon E. Smith" , freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Network memory allocation failures X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2010 22:02:30 -0000 On Tue, Sep 7, 2010 at 4:08 PM, Mahlon E. Smith wrote: > I've kind of reached a limit here in what to dig for / try next. What > else can I do to try and determine the root problem that would be > helpful? Anyone ever have to deal with or seen something like this > recently? (Or hell, not recently?) > > Ideas appreciated! > Wild guess here, not sure all the dynamics of changing this, but you could try increasing: kern.maxdsiz It's a kern tunable, so change it in /boot/loader.conf -- Adam Vande More