[dpdk-users] Fwd: Issues binding 82545EM to igb

DPDK usage discussions
 help / color / mirror / Atom feed

* [dpdk-users] Fwd: Issues binding 82545EM to igb_uio on Centos 6.5 + DPDK 16.07
       [not found] <CAFxVZ5J7HP_f9HAFicdbHXji=mgo8Lt23w0Rhd3CA1b6TKFeNQ@mail.gmail.com>
@ 2016-11-03 22:38 ` Sruthi Yellamraju
  0 siblings, 0 replies; only message in thread
From: Sruthi Yellamraju @ 2016-11-03 22:38 UTC (permalink / raw)
  To: users

Hi,

I have a 82545EM NIC running e1000 driver on a VM running Centos 6.5 build
(2.6.32-431.20.3.el6.x86_64) (See lspci O/p). I am using dpdk-16.07 and
when i try binding this device to igb_uio, its giving me the following
error. Any pointers? I was able to get other drivers fm10k, e1000e to work
with this kernel version, but not e1000.

#dpdk-devbind -b igb_uio 0000:02:01.0
Error: bind failed for 0000:02:01.0 - Cannot bind to driver igb_uio

dmesg shows:

Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INT A ->
GSI 19 (level, low) -> IRQ 19
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: setting
latency timer to 64
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INTX mask
not supported
Nov  3 08:57:16 vm-sensor-test1 kernel: IRQ handler type mismatch for IRQ 0
Nov  3 08:57:16 vm-sensor-test1 kernel: current handler: timer
Nov  3 08:57:16 vm-sensor-test1 kernel: Pid: 3976, comm: dpdk-devbind Not
tainted 2.6.32-431.20.3.el6.x86_64 #1
Nov  3 08:57:16 vm-sensor-test1 kernel: Call Trace:
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff810e7dd2>] ?
__setup_irq+0x382/0x3c0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa00692b0>] ?
uio_interrupt+0x0/0x48 [uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff810e85d3>] ?
request_threaded_irq+0x133/0x230
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa00691ce>] ?
__uio_register_device+0x58e/0x620 [uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa003269c>] ?
igbuio_pci_probe+0x3e1/0x500 [igb_uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81284f9a>] ?
kobject_get+0x1a/0x30
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a5747>] ?
local_pci_probe+0x17/0x20
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a6931>] ?
pci_device_probe+0x101/0x120
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e102>] ?
driver_sysfs_add+0x62/0x90
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e2a0>] ?
driver_probe_device+0xa0/0x2a0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e54b>] ?
__driver_attach+0xab/0xb0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e4a0>] ?
__driver_attach+0x0/0xb0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136d854>] ?
bus_for_each_dev+0x64/0x90
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e03e>] ?
driver_attach+0x1e/0x20
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a6cd7>] ?
pci_add_dynid+0xc7/0xf0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a6dd2>] ?
store_new_id+0xd2/0x110
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136c87c>] ?
drv_attr_store+0x2c/0x30
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81204685>] ?
sysfs_write_file+0xe5/0x170
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81188df8>] ?
vfs_write+0xb8/0x1a0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff811896f1>] ?
sys_write+0x51/0x90
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8100b072>] ?
system_call_fastpath+0x16/0x1b
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INT A
disabled
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio: probe of 0000:02:01.0
failed with error -16
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INT A ->
GSI 19 (level, low) -> IRQ 19
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: setting
latency timer to 64
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INTX mask
not supported
Nov  3 08:57:16 vm-sensor-test1 kernel: IRQ handler type mismatch for IRQ 0
Nov  3 08:57:16 vm-sensor-test1 kernel: current handler: timer
Nov  3 08:57:16 vm-sensor-test1 kernel: Pid: 3976, comm: dpdk-devbind Not
tainted 2.6.32-431.20.3.el6.x86_64 #1
Nov  3 08:57:16 vm-sensor-test1 kernel: Call Trace:
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff810e7dd2>] ?
__setup_irq+0x382/0x3c0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa00692b0>] ?
uio_interrupt+0x0/0x48 [uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff810e85d3>] ?
request_threaded_irq+0x133/0x230
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa00691ce>] ?
__uio_register_device+0x58e/0x620 [uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffffa003269c>] ?
igbuio_pci_probe+0x3e1/0x500 [igb_uio]
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81284f9a>] ?
kobject_get+0x1a/0x30
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a5747>] ?
local_pci_probe+0x17/0x20
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff812a6931>] ?
pci_device_probe+0x101/0x120
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e102>] ?
driver_sysfs_add+0x62/0x90
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136e2a0>] ?
driver_probe_device+0xa0/0x2a0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136d7aa>] ?
driver_bind+0xca/0x110
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8136c87c>] ?
drv_attr_store+0x2c/0x30
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81204685>] ?
sysfs_write_file+0xe5/0x170
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff81188df8>] ?
vfs_write+0xb8/0x1a0
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff811896f1>] ?
sys_write+0x51/0x90
Nov  3 08:57:16 vm-sensor-test1 kernel: [<ffffffff8100b072>] ?
system_call_fastpath+0x16/0x1b
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio 0000:02:01.0: PCI INT A
disabled
Nov  3 08:57:16 vm-sensor-test1 kernel: igb_uio: probe of 0000:02:01.0
failed with error -16

lspci o/p
=======
02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet
Controller (Copper) (rev 01)
        Subsystem: VMware PRO/1000 MT Single Port Adapter
        Physical Slot: 33
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0 (63750ns min), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at fd5c0000 (64-bit, non-prefetchable) [size=128K]
        Region 2: Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at 2000 [size=64]
        [virtual] Expansion ROM at e7b00000 [disabled] [size=64K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [e4] PCI-X non-bridge device
                Command: DPERE- ERO+ RBC=512 OST=1
                Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple
DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
        Kernel driver in use: e1000
        Kernel modules: e1000

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-11-03 22:38 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAFxVZ5J7HP_f9HAFicdbHXji=mgo8Lt23w0Rhd3CA1b6TKFeNQ@mail.gmail.com>
2016-11-03 22:38 ` [dpdk-users] Fwd: Issues binding 82545EM to igb_uio on Centos 6.5 + DPDK 16.07 Sruthi Yellamraju

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).