From owner-freebsd-net@FreeBSD.ORG Wed Mar 30 16:44:37 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 7CCC8106564A for ; Wed, 30 Mar 2011 16:44:37 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 39941158A95; Wed, 30 Mar 2011 16:44:37 +0000 (UTC) Message-ID: <4D935DF6.90906@FreeBSD.org> Date: Wed, 30 Mar 2011 09:44:38 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Arnaud Lacombe References: <4D923931.2070606@zonov.org> <4D92BB71.5000900@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: igb(4) won't start with "igb0: Could not setup receive structures" 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: Wed, 30 Mar 2011 16:44:37 -0000 On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: > Hi, > > On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton wrote: > The only things I've been able to get from Jack is "We, at Intel, test > em(4) at 256k nmbclusters. We do not have problem. If you have > problem, raise nmbcluster.". 256k nmbcluster in my environment is not > acceptable. > >> Meanwhile, there are times where memory IS a constraint, and there are some >> things you can't do without more of it. >> > yes, but the driver should not need a manual reset between the time > resource are (heavily) scarce and the time it became available again. If you're facing that situation then obviously your system is constrained by hardware. It sounds like you have 3 choices: 1. Add more RAM 2. Use a different NIC 3. Set MTU lower I'm sorry to say that just because the software is free doesn't mean that we can guarantee that it will work on all hardware. Sometimes the physical limits of the hardware are what need to be changed. Good luck, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/