On 2015-5-20, at 17:42, Ryan Stone ryst...@gmail.com wrote:
Oh, I bet that you have a bunch of CPUs and ixl is consuming all of your
interrupt vectors. Does setting this tunable fix the issue?
hw.ixl.max_queues=1
Yeah, this box has 40 cores, but unfortunately that tunable doesn't change
Oh, I bet that you have a bunch of CPUs and ixl is consuming all of your
interrupt vectors. Does setting this tunable fix the issue?
hw.ixl.max_queues=1
___
freebsd-current@freebsd.org mailing list
On 2015-5-18, at 19:22, Ryan Stone ryst...@gmail.com wrote:
Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My
hardware is a little different from yours -- my CPU is a Haswell Xeon, and I
have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I
didn't
On 2015-5-18, at 16:08, Ryan Stone ryst...@gmail.com wrote:
This is very strange. I have successfully netbooted -CURRENT in a very
similar environment (ixl compiled into kernel and booting over igb). I
can't remember when the last time I did this but it was probably within the
last couple of
Hi,
when I have the ixl driver compiled into my -CURRENT kernel (or loaded as a
module via loader.conf), the boot seems to hang (or silently crash) when BOOTP
starts bringing up interfaces to send out probes. (I'm not netbooting over an
ixl, the boot interface is an igb.)
What works is
On Mon, May 18, 2015 at 8:40 AM, Eggert, Lars l...@netapp.com wrote:
Hi,
when I have the ixl driver compiled into my -CURRENT kernel (or loaded as
a module via loader.conf), the boot seems to hang (or silently crash) when
BOOTP starts bringing up interfaces to send out probes. (I'm not
On Mon, May 18, 2015 at 10:08 AM, Ryan Stone ryst...@gmail.com wrote:
I can't remember when the last time I did this but it was probably within
the last couple of weeks.
Pardon me, I meant months, not weeks.
___
freebsd-current@freebsd.org mailing
On Mon, May 18, 2015 at 12:30 PM, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Mon, May 18, 2015 at 02:42:51PM +, Eggert, Lars wrote:
Legacy mode, and it hangs in the kernel.
Without if_ixl in loader.conf, it does the usual BOOTP logic:
^^^ ^^
Sending DHCP Discover
Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My
hardware is a little different from yours -- my CPU is a Haswell Xeon, and
I have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I
didn't have Xen or anything running.
On Mon, May 18, 2015 at 02:42:51PM +, Eggert, Lars wrote:
Legacy mode, and it hangs in the kernel.
Without if_ixl in loader.conf, it does the usual BOOTP logic:
^^^ ^^
Sending DHCP Discover packet from interface ix0 (90:e2:ba:77:d4:9c)
10 matches
Mail list logo