From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ferruh.yigit@intel.com> Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 237A4325C; Wed, 15 Nov 2017 16:44:38 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Nov 2017 07:44:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,399,1505804400"; d="scan'208";a="2156474" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.254.93.35]) ([10.254.93.35]) by FMSMGA003.fm.intel.com with ESMTP; 15 Nov 2017 07:44:35 -0800 To: Gregory Etelson <gregory@weka.io> Cc: Chas Williams <3chas3@gmail.com>, Thomas Monjalon <thomas@monjalon.net>, stable@dpdk.org, dev <dev@dpdk.org>, Jianfeng Tan <jianfeng.tan@intel.com>, Jingjing Wu <jingjing.wu@intel.com>, Shijith Thotton <shijith.thotton@caviumnetworks.com>, Harish Patil <harish.patil@cavium.com>, George Prekas <george.prekas@epfl.ch>, Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>, Rasesh Mody <rasesh.mody@cavium.com>, Lee Roberts <lee.roberts@hpe.com>, Stephen Hemminger <stephen@networkplumber.org> References: <20171103223822.28852-1-ferruh.yigit@intel.com> <2004961.P5XXAOnQC2@xps> <CAG2-Gkk1Z3ZE3XpyK_FQVLnQb9qeY3tYnny6n9x2m2E0MkFRyA@mail.gmail.com> <1866566.0zvbrY6xpu@polaris> <0465168a-d7ce-8589-1f34-cf905f7069f6@intel.com> <CAO--2fFLqLNBcNja-HgYVYLfF3zpcLPspVz908JUUEaF25HMWw@mail.gmail.com> From: Ferruh Yigit <ferruh.yigit@intel.com> Message-ID: <7c857b64-dfb4-6fb9-c8de-bb41a17dd4bf@intel.com> Date: Wed, 15 Nov 2017 07:44:34 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <CAO--2fFLqLNBcNja-HgYVYLfF3zpcLPspVz908JUUEaF25HMWw@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-stable] ugb_uio: r3.8xlarge bind failure X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches <stable.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/stable>, <mailto:stable-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/stable/> List-Post: <mailto:stable@dpdk.org> List-Help: <mailto:stable-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/stable>, <mailto:stable-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 15 Nov 2017 15:44:39 -0000 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 > 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 <ferruh.yigit@intel.com > <mailto:ferruh.yigit@intel.com>> 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: > > [<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 > > > >