Re: [E1000-devel] SR-IOV: IGB/IGBVF initialisation problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 22, 2009 at 08:55:10AM -0700, Duyck, Alexander H wrote:
> Simon Horman wrote:
> > I did managed to get a bit further using Yu Zhao's suggestion of
> > using the pci=assign-busses boot option. With that in effect I get:
> > 
> > $ modprobe igb max_vfs=1
> > dca service started, version 1.8
> > Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
> > Copyright (c) 2007-2009 Intel Corporation.
> > igb 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> > igb 0000:01:00.0: 1 vfs allocated
> > Intel(R) Virtual Function Network Driver - version 1.0.0-k0
> > Copyright (c) 2009 Intel Corporation.
> > igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
> > igb 0000:01:00.0: eth3: (PCIe:2.5Gb/s:Width x4) 00:1b:21:2f:16:84
> > igb 0000:01:00.0: eth3: PBA No: e43709-003
> > igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
> > igbvf 0000:02:10.0: enabling device (0000 -> 0002)
> > igbvf 0000:02:10.0: PF still in reset state, assigning new address
> > igbvf 0000:02:10.0: PF still resetting
> > igbvf 0000:02:10.0: Intel(R) 82576 Virtual Function
> > igbvf 0000:02:10.0: Address: 26:32:a2:c5:bb:97
> > igbvf 0000:02:10.0: MAC: 1
> > igb 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> > igbvf 0000:02:10.1: enabling device (0000 -> 0002)
> > igbvf 0000:02:10.1: PF still in reset state, assigning new address
> > igbvf 0000:02:10.1: PF still resetting
> > igbvf 0000:02:10.1: Intel(R) 82576 Virtual Function
> > igbvf 0000:02:10.1: Address: fa:24:e0:85:d7:20
> > igbvf 0000:02:10.1: MAC: 1
> > igb 0000:01:00.1: 1 vfs allocated
> > igb 0000:01:00.1: Intel(R) Gigabit Ethernet Network Connection
> > igb 0000:01:00.1: eth5: (PCIe:2.5Gb/s:Width x4) 00:1b:21:2f:16:85
> > igb 0000:01:00.1: eth5: PBA No: e43709-003
> > igb 0000:01:00.1: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
> > 
> > However the PF resetting messages seem to be of concern and
> > the resulting NICs don't seem to get any packets.
> >
> 
> Actually all this indicates is that the PF has not been brought up and is
> likely still down.  You just need to do an 'ifconfig eth3 up' and then
> the VF on 02:10.0 should show link as well when it is brought up.

Thanks, that seems to have done the trick.

--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux