Re: [dpdk-dev] ugb_uio: r3.8xlarge bind failure

2017-11-15 Thread Gregory Etelson
Hello Ferruh, re-checked igb_uio from dpdk master branch 0384f21dffc9081d1ae30f0a6e49926bfc4be85d OS: CentOS release 6.7 (Final), 2.6.32-573.26.1.el6.x86_64 igb_uio: Use MSIX interrupt by default ixgbevf: eth1: ixgbevf_remove: Remove complete IRQ handler type mismatch for IRQ 0 current handler: t

Re: [dpdk-dev] ugb_uio: r3.8xlarge bind failure

2017-11-15 Thread Ferruh Yigit
On 11/9/2017 10:36 PM, Gregory Etelson wrote: > It looks like igb_uio bind failed on servers running CentOS-6.x Hi Gregory, Below backtrace seems coming from old code, can you please confirm that you are using latest igb_uio? And what is the kernel version in that boxes? Thanks, ferruh > Serve

Re: [dpdk-dev] ugb_uio: r3.8xlarge bind failure

2017-11-09 Thread Gregory Etelson
It looks like igb_uio bind failed on servers running CentOS-6.x Servers with CentOS-7.3 Ubuntu-14, Ubuntu-16 and AWS-1703 (Amazon Linux) had no bind issues Regards, Gregory On Fri, Nov 10, 2017 at 3:42 AM, Ferruh Yigit wrote: > On 11/9/2017 9:20 AM, Gregory Etelson wrote: > > Hello, > > > > The

Re: [dpdk-dev] ugb_uio: r3.8xlarge bind failure

2017-11-09 Thread Ferruh Yigit
On 11/9/2017 9:20 AM, Gregory Etelson wrote: > Hello, > > There are some AWS R3.8XLARGE instances > that fail to bind Intel 10G VFs with igb_uio [c05cb4f939082]. Hi Gregory, Will you dig this issue more? Please keep us updated. > System dmeg log show this backtrace: > > igb_uio: probe of 000

[dpdk-dev] ugb_uio: r3.8xlarge bind failure

2017-11-09 Thread Gregory Etelson
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 :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