Hi,
I just popped a new four-port igb card into a -STABLE system and encountered
severe issues even when unloaded right after boot, to the point where I
couldn't even ssh into the system anymore. The box has 2x4 cores:
CPU: Intel(R) Xeon(R) CPU X5450 @ 3.00GHz (2992.60-MHz K8-class
On 20.06.2013 17:34, Eggert, Lars wrote:
real memory = 8589934592 (8192 MB)
avail memory = 8239513600 (7857 MB)
By default, the igb driver seems to set up one queue per detected CPU.
Googling around, people seemed to suggest that limiting the number of queues
makes things work better. I
On 20.06.2013 15:37, Eugene Grosbein wrote:
On 20.06.2013 17:34, Eggert, Lars wrote:
real memory = 8589934592 (8192 MB)
avail memory = 8239513600 (7857 MB)
By default, the igb driver seems to set up one queue per detected CPU. Googling
around, people seemed to suggest that limiting the
--- On Thu, 6/20/13, Andre Oppermann wrote:
gt; From: Andre Oppermann
gt; Subject: Re: hw.igb.num_queues default
gt; To: quot;Eugene Grosbeinquot;
gt; Cc: quot;freebsd-net@freebsd.orgquot; , quot;Eggert, Larsquot; ,
quot;Jack Vogelquot;
gt; Date: Thursday, June 20, 2013, 10:29 AM
gt
Hi,
On Jun 20, 2013, at 16:29, Andre Oppermann an...@freebsd.org wrote:
On 20.06.2013 15:37, Eugene Grosbein wrote:
Or, better, make nmbclusters auto-tuning smarter, if any.
I mean, use more nmbclusters for machines with large amounts of memory.
That has already been done in HEAD.
the box
On Jun 20, 2013, at 17:51, Eggert, Lars l...@netapp.com wrote:
the box in question is running -CURRENT, so that may also still help.
s/CURRENT/STABLE/
Frankly, I don't really care what the correct fix is. I just want to be able
to plop this NIC in and be able to connect to it without the
