Hello,
There are some AWS R3.8XLARGE instances
that fail to bind Intel 10G VFs with igb_uio [c05cb4f939082].
System dmeg log show this backtrace:
igb_uio: probe of 0000:00:05.0 failed with error -16
IRQ handler type mismatch for IRQ 0
current handler: timer
Pid: 3619, comm: bash Not tainted 2.6.32-642.15.1.el6.x86_64 #1
Call Trace:
[<ffffffff810f49e2>] ? __setup_irq+0x382/0x3c0
[<ffffffffa03202a0>] ? uio_interrupt+0x0/0x48 [uio]
[<ffffffff810f51e3>] ? request_threaded_irq+0x133/0x230
[<ffffffffa0320193>] ? __uio_register_device+0x553/0x610 [uio]
[<ffffffffa032698f>] ? igbuio_pci_probe+0x290/0x47a [igb_uio]
[<ffffffff8129d00a>] ? kobject_get+0x1a/0x30
[<ffffffff812c04f7>] ? local_pci_probe+0x17/0x20
[<ffffffff812c16e1>] ? pci_device_probe+0x101/0x120
[<ffffffff81382152>] ? driver_sysfs_add+0x62/0x90
[<ffffffff813823fa>] ? driver_probe_device+0xaa/0x3a0
[<ffffffff8138153a>] ? driver_bind+0xca/0x110
[<ffffffff813805dc>] ? drv_attr_store+0x2c/0x30
[<ffffffff812171c5>] ? sysfs_write_file+0xe5/0x170
[<ffffffff81199e48>] ? vfs_write+0xb8/0x1a0
[<ffffffff8119b336>] ? fget_light_pos+0x16/0x50
[<ffffffff8119a981>] ? sys_write+0x51/0xb0
The VFs can be returned back to kernel ixgbevf driver with no faults.
The instances can bind VFs with igb_uio[b58eedfc7dd57]
I could not find yet why some R3.8XLARGE instances can bind IXGBE VFs with
igb_uio while other fail
lspci -vvv -s 0000:00:05.0
00:05.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller
Virtual Function (rev 01)
Physical Slot: 5
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Region 0: Memory at f3010000 (64-bit, prefetchable) [size=16K]
Region 3: Memory at f3014000 (64-bit, prefetchable) [size=16K]
Capabilities: [70] MSI-X: Enable+ Count=3 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
Kernel driver in use: ixgbevf
Kernel modules: ixgbevf
Regards,
Gregory
