Date: Wed, 30 Mar 2011 09:44:38 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Arnaud Lacombe <lacombar@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: igb(4) won't start with "igb0: Could not setup receive structures" Message-ID: <4D935DF6.90906@FreeBSD.org> In-Reply-To: <AANLkTi=z3J2ddUJ%2BcwCD3YWuy8L973k9foC0SQLgTGRC@mail.gmail.com> References: <4D923931.2070606@zonov.org> <AANLkTimnnDbtVVaK=yhozEmqxTAp3hudNbEVA6F6pbnq@mail.gmail.com> <4D92BB71.5000900@FreeBSD.org> <AANLkTi=z3J2ddUJ%2BcwCD3YWuy8L973k9foC0SQLgTGRC@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: > Hi, > > On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton<dougb@freebsd.org> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D935DF6.90906>