On Wed, 5 Sep 2012 18:46:11 +0530
Mohit Dhingra <mohitdhing...@gmail.com> wrote:

> *Hi Greg,*
> 
> I took so many days to figure out how to run Xen-supported kernel and
> then I switched on CONFIG_PCI_REALLOC_ENABLE_AUTO=y also in
> kernel .config. But still I see the same error :(  (SR-IOV: bus
> number out of range)
> 
> I am attaching the .config file also.
> 
> dmesg | grep igb gives me following :
> [    9.193184] kobject: 'igb' (ffffffffa019a310):
> kobject_add_internal: parent: 'module', set: 'module'
> [    9.193193] kobject: 'holders' (ffff880218de0f40):
> kobject_add_internal: parent: 'igb', set: '<NULL>'
> [    9.193233] kobject: 'notes' (ffff8802169d69c0):
> kobject_add_internal: parent: 'igb', set: '<NULL>'
> [    9.193239] kobject: 'igb' (ffffffffa019a310): kobject_uevent_env
> [    9.193244] kobject: 'igb' (ffffffffa019a310): fill_kobj_path:
> path = '/module/igb'
> [    9.193925] igb: Intel(R) Gigabit Ethernet Network Driver - version
> 3.4.7-k
> [    9.193928] igb: Copyright (c) 2007-2012 Intel Corporation.
> [    9.193935] kobject: 'igb' (ffff88021aded5c0):
> kobject_add_internal: parent: 'drivers', set: 'drivers'
> [    9.194698] igb 0000:03:00.0: SR-IOV: bus number out of range
> [    9.385286] igb 0000:03:00.0: added PHC on eth1
> [    9.385291] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network
> Connection
> [    9.385296] igb 0000:03:00.0: eth1: (PCIe:2.5Gb/s:Width x4)
> 00:1b:21:8f:bd:20
> [    9.385381] igb 0000:03:00.0: eth1: PBA No: E66339-003
> [    9.385386] igb 0000:03:00.0: Using MSI-X interrupts. 2 rx
> queue(s), 1 tx queue(s)
> [    9.386267] igb 0000:03:00.1: SR-IOV: bus number out of range
> [    9.577215] igb 0000:03:00.1: added PHC on eth2
> [    9.577218] igb 0000:03:00.1: Intel(R) Gigabit Ethernet Network
> Connection
> [    9.577222] igb 0000:03:00.1: eth2: (PCIe:2.5Gb/s:Width x4)
> 00:1b:21:8f:bd:21
> [    9.577306] igb 0000:03:00.1: eth2: PBA No: E66339-003
> [    9.577309] igb 0000:03:00.1: Using MSI-X interrupts. 2 rx
> queue(s), 1 tx queue(s)
> [    9.578086] igb 0000:04:00.0: SR-IOV: bus number out of range
> [    9.769213] igb 0000:04:00.0: added PHC on eth3
> [    9.769217] igb 0000:04:00.0: Intel(R) Gigabit Ethernet Network
> Connection
> [    9.769221] igb 0000:04:00.0: eth3: (PCIe:2.5Gb/s:Width x4)
> 00:1b:21:8f:bd:24
> [    9.769305] igb 0000:04:00.0: eth3: PBA No: E66339-003
> 
> 
> [    9.769308] igb 0000:04:00.0: Using MSI-X interrupts. 2 rx
> queue(s), 1 tx queue(s)
> 
> [    9.770095] igb 0000:04:00.1: SR-IOV: bus number out of range
> 
> 
> [    9.961215] igb 0000:04:00.1: added PHC on eth4
> 
> 
> [    9.961218] igb 0000:04:00.1: Intel(R) Gigabit Ethernet Network
> Connection
> [    9.961221] igb 0000:04:00.1: eth4: (PCIe:2.5Gb/s:Width x4)
> 00:1b:21:8f:bd:25
> [    9.961306] igb 0000:04:00.1: eth4: PBA No: E66339-003
> [    9.961310] igb 0000:04:00.1: Using MSI-X interrupts. 2 rx
> queue(s), 1 tx queue(s)
> [    9.961354] kobject: 'drivers' (ffff88021a1b8600):
> kobject_add_internal: parent: 'igb', set: '<NULL>'
> [    9.961368] kobject: 'igb' (ffff88021aded5c0): kobject_uevent_env
> [    9.961373] kobject: 'igb' (ffff88021aded5c0): fill_kobj_path:
> path = '/bus/pci/drivers/igb'
> [   19.309312] igb: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow
> Control: RX
> 
> 
> I am booting the kernel as following :
> title Xen+ -- openSUSE 11.4 - 3.5.0-0.11 SR - IOV
>     root (hd0,6)
>     kernel /boot/xen.gz vga=mode-0x317 intel_iommu=on msi=on iommu=on
>     module /boot/vmlinuz-3.5.0-0.11-xen+
> root=/dev/disk/by-id/ata-ST31000528AS_9VP9NG6C-part7
> resume=/dev/disk/by-id/ata-ST31000528AS_9VP9NG6C-part5 splash=silent
> quiet showopts vga=0x317
>     module /boot/initrd-3.5.0-0.11-xen+
> 
> 
> Does that mean I can not run SR-IOV on this machine? :-\
> 

Unfortunately I can't prove a negative and say for sure that the
machine cannot run SR-IOV but it does appear that you've done all the
usual configuration in the kernel that should make it work and it still
does not.  In every case I've seen it is due to a BIOS that just can't
support SR-IOV.  What I can say positively is that the issue is not
with our driver and I suspect that any other SR-IOV capable device you
might try in the machine would not work either.

I wish I had better news for you.

Regards,

- Greg

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to