sr-iov issues, reset_hw() failed with error -100

2016-02-20 Thread Ultima
#x27;Intel Corporation' device = 'X540 Ethernet Controller Virtual Function' class = network subclass = ethernet ppt26@pci0:129:0:185: class=0x02 card=0x1458 chip=0x15158086 rev=0x01 hdr=0x00 vendor = 'Intel Cor

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-22 Thread Ultima
options=21 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair On Mon, Feb 22, 2016 at 1:51 PM, Eric Joyner wrote: > Did you do an ifconfig up on ix1 before loading the VF driver? > > On Sat, Feb 20, 2016 at 11:57 AM Ultima wrote: > >> Decided to do some testing with

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-22 Thread Ultima
This system has 24 cores (e5-2670v3)x2 Ultima On Mon, Feb 22, 2016 at 3:53 PM, Pieper, Jeffrey E < jeffrey.e.pie...@intel.com> wrote: > Just out of curiosity, how many cores does your system have? > > Jeff > > -Original Message- > From: owner-freebsd-curr...@free

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-22 Thread Ultima
Yeah, dmesg does show 48. 12 Cores and 24 threads each. 48 total On Mon, Feb 22, 2016 at 4:35 PM, Steven Hartland wrote: > isn't that 48 cores (12 real 12 virtual) per CPU? > > > On 22/02/2016 21:26, Ultima wrote: > >> This system has 24 cores (e5-2670v3)x2 >>

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-22 Thread Ultima
er received. I'v already double checked VT-d, but I'll make it tripple! =] I can't reset the system right now, but ill send an update when possible with only 2 vf's and unmodified generic. Ultima On Mon, Feb 22, 2016 at 8:52 PM, Eric Joyner wrote: > I don't really h

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-23 Thread Ultima
in bios likely played a role in this. If you have any ideas, I'm willing to test them. Thanks! =] VT-d screen: https://puu.sh/niyiq/4fee92e4a3.jpgn PCI advanced options: https://puu.sh/niyjg/88e71e48d9.jpgn Ultima On Mon, Feb 22, 2016 at 9:46 PM, Ultima wrote: > I forgot to mention

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-24 Thread Ultima
t think I listed the motherboards in question yet so ill list them now. S1200BTLRM - http://ark.intel.com/products/69633/Intel-Server-Board-S1200BTLRM?q=S1200BTLRM MD80-TM0 - http://b2b.gigabyte.com/products/product-page.aspx?pid=5146#ov I'm not sure if it will be

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-24 Thread Ultima
F driver? > > I've tried SR-IOV on a system here, and I can confirm that traffic stops > passing on the PF interface when you create a VF interface. That didn't > used to happen, so I'm investigating why that is right now. > > On Wed, Feb 24, 2016 at 8:09 AM Ultima wrot

Re: sr-iov issues, reset_hw() failed with error -100

2016-03-09 Thread Ultima
if you're still interested in this, but did you do "kenv > hw.vmm.force_iommu=1" before loading the vmm module? I think that might be > necessary. > > On Wed, Feb 24, 2016 at 5:12 PM Ultima wrote: > >> Yeah, still getting the -100 error, I do have sendmail disable

Re: sr-iov issues, reset_hw() failed with error -100

2016-03-28 Thread Ultima
returned 5 ixv0: at device 0.129 on pci12 ixv0: Using MSIX interrupts with 2 vectors ixv0: ixgbe_reset_hw() failed with error -100 device_attach: ixv0 attach returned 5 On Wed, Mar 9, 2016 at 5:36 PM, Ultima wrote: > I have been interested in this when I first read about it in 2012. =] >

ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100)

2016-04-24 Thread Ultima
ut error # dmesg ixv0: at device 0.129 numa-domain 1 on pci12 ixv0: Using MSIX interrupts with 2 vectors ixv0: ixgbe_reset_hw() failed with error -100 device_attach: ixv0 attach returned 5 # cat /etc/iovctl.conf PF { device : ix1; num_vfs : 31; } DEFAULT { passthrough : true; }

Re: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100)

2016-04-28 Thread Ultima
Jeb, Okay, just wanted to make sure it was known. =] Ultima On Thu, Apr 28, 2016 at 4:36 PM, cramerj wrote: > Yeah, we're running into some issues with our implementation. I'm working > on the VF driver now and hope to get some of these bugs fixed within the > next coupl