From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gregory@weka.io>
Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48])
 by dpdk.org (Postfix) with ESMTP id E03901B20E
 for <dev@dpdk.org>; Thu,  9 Nov 2017 18:20:59 +0100 (CET)
Received: by mail-wm0-f48.google.com with SMTP id t139so19274109wmt.1
 for <dev@dpdk.org>; Thu, 09 Nov 2017 09:20:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weka.io; s=google;
 h=from:to:reply-to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=mFAU2VpuCmVHz32u1lTdcdtLVpoVlvPAJR3xuSq8rBY=;
 b=mQl53/lwrUgYi3EJcBOdin52oiXrnjuxlcBvL1+v2T0jYPLCFOJB5hP+HA4kYfkdi+
 1IPEB6banfCESRaC9vEiiTu/rK4XK9c266qKDAloPBDOObq3T8G3JQq90Yul4e8Nv+NQ
 sibiaS8liPwhJkqIigIRVS5Vl5CTEH9D+5gT0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:reply-to:cc:subject:date:message-id
 :in-reply-to:references:mime-version:content-transfer-encoding;
 bh=mFAU2VpuCmVHz32u1lTdcdtLVpoVlvPAJR3xuSq8rBY=;
 b=h0kqnLRt8NMFxX94bx7pXFITBhQxB8XjmgO7WdcC+4ode9eDmZXvnvzyRJVCDExWpW
 ECBTnTHUFDG0UbIR6DFFxF8sY16qNVP31XAHDjThx3/jqLGXin3JeoCoPONV/YpYZv1r
 EuBqzJrqvIDb5lQax8nAIYh+7DJBi3eROMmrMlr+m4fWEYhyzK2iDtrfvfiLNrnjYLqJ
 st51xk5mAMqC/PbM9HQC8zDkhIYBkpwDJNXrFFf56HI7z+RVPNIy7CkCXBe3N8s4GiRJ
 qtmkHnVRK1xf5k+Ef02p8sq9+Bb1P/Kv0ITApW4oMXu98sdlltFQcNiEPP9MLSDqGKqk
 pXaw==
X-Gm-Message-State: AJaThX6sIEWbKHOIX5gzl/RTyXEjmd3xuLHxsZDa5d3KnRLEUMESw9y4
 QUfsIiotIkA/0tRhd//rdyfFbw==
X-Google-Smtp-Source: ABhQp+QwufFPP12XBu3NQ2b+Dm3xUegvzqn8ZPymR3E0czH0ImhnWCG9ploHCI3BbRTiqlSpHM5o0A==
X-Received: by 10.80.204.154 with SMTP id q26mr1699498edi.108.1510248059305;
 Thu, 09 Nov 2017 09:20:59 -0800 (PST)
Received: from polaris.localnet (bzq-84-109-69-99.red.bezeqint.net.
 [84.109.69.99])
 by smtp.gmail.com with ESMTPSA id s56sm6676223edm.86.2017.11.09.09.20.58
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 09 Nov 2017 09:20:58 -0800 (PST)
From: Gregory Etelson <gregory@weka.io>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Chas Williams <3chas3@gmail.com>, Thomas Monjalon <thomas@monjalon.net>,
 stable@dpdk.org, 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>
Date: Thu, 09 Nov 2017 19:20:56 +0200
Message-ID: <1866566.0zvbrY6xpu@polaris>
In-Reply-To: <CAG2-Gkk1Z3ZE3XpyK_FQVLnQb9qeY3tYnny6n9x2m2E0MkFRyA@mail.gmail.com>
References: <20171103223822.28852-1-ferruh.yigit@intel.com>
 <2004961.P5XXAOnQC2@xps>
 <CAG2-Gkk1Z3ZE3XpyK_FQVLnQb9qeY3tYnny6n9x2m2E0MkFRyA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: [dpdk-dev] ugb_uio: r3.8xlarge bind failure
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gregory@weka.io
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Nov 2017 17:21:00 -0000

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