Date: Wed, 30 Mar 2011 13:06:56 -0400 From: Arnaud Lacombe <lacombar@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: igb(4) won't start with "igb0: Could not setup receive structures" Message-ID: <AANLkTimpoWBUcjKx3rRgwGYb31aush0_AkrULrPA%2BEk9@mail.gmail.com> In-Reply-To: <4D935DF6.90906@FreeBSD.org> References: <4D923931.2070606@zonov.org> <AANLkTimnnDbtVVaK=yhozEmqxTAp3hudNbEVA6F6pbnq@mail.gmail.com> <4D92BB71.5000900@FreeBSD.org> <AANLkTi=z3J2ddUJ%2BcwCD3YWuy8L973k9foC0SQLgTGRC@mail.gmail.com> <4D935DF6.90906@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Wed, Mar 30, 2011 at 12:44 PM, Doug Barton <dougb@freebsd.org> wrote: > 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> =A0wrote= : > >> 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. No. We are taking about exceptional recoverable situation not handled by the software, it should not bring the complete system down. If you're swapping code has defect, you do not tell one to buy more RAM not to trigger the defective code, you fix the code. The situation is similar here. - Arnaud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimpoWBUcjKx3rRgwGYb31aush0_AkrULrPA%2BEk9>