From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory Etelson Subject: Re: ugb_uio: r3.8xlarge bind failure Date: Fri, 10 Nov 2017 08:36:15 +0200 Message-ID: References: <20171103223822.28852-1-ferruh.yigit@intel.com> <2004961.P5XXAOnQC2@xps> <1866566.0zvbrY6xpu@polaris> <0465168a-d7ce-8589-1f34-cf905f7069f6@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Chas Williams <3chas3@gmail.com>, Thomas Monjalon , stable@dpdk.org, dev , Jianfeng Tan , Jingjing Wu , Shijith Thotton , Harish Patil , George Prekas , Sergio Gonzalez Monroy , Rasesh Mody , Lee Roberts , Stephen Hemminger To: Ferruh Yigit Return-path: Received: from mail-vk0-f65.google.com (mail-vk0-f65.google.com [209.85.213.65]) by dpdk.org (Postfix) with ESMTP id C56E21B66C for ; Fri, 10 Nov 2017 07:36:16 +0100 (CET) Received: by mail-vk0-f65.google.com with SMTP id t184so5511108vka.6 for ; Thu, 09 Nov 2017 22:36:16 -0800 (PST) In-Reply-To: <0465168a-d7ce-8589-1f34-cf905f7069f6@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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, > > > > 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 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: > > [] ? __setup_irq+0x382/0x3c0 > > [] ? uio_interrupt+0x0/0x48 [uio] > > [] ? request_threaded_irq+0x133/0x230 > > [] ? __uio_register_device+0x553/0x610 [uio] > > [] ? igbuio_pci_probe+0x290/0x47a [igb_uio] > > [] ? kobject_get+0x1a/0x30 > > [] ? local_pci_probe+0x17/0x20 > > [] ? pci_device_probe+0x101/0x120 > > [] ? driver_sysfs_add+0x62/0x90 > > [] ? driver_probe_device+0xaa/0x3a0 > > [] ? driver_bind+0xca/0x110 > > [] ? drv_attr_store+0x2c/0x30 > > [] ? sysfs_write_file+0xe5/0x170 > > [] ? vfs_write+0xb8/0x1a0 > > [] ? fget_light_pos+0x16/0x50 > > [] ? 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- > > SERR- > 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 > > > >