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 <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>
Subject: Re: [dpdk-stable] ugb_uio: r3.8xlarge bind failure
Date: Wed, 15 Nov 2017 18:30:44 +0200 [thread overview]
Message-ID: <CAO--2fH=oj73C+0Er6rnmKRxrXXMaqdheDo6+B-SSGOF0oqxew@mail.gmail.com> (raw)
In-Reply-To: <7c857b64-dfb4-6fb9-c8de-bb41a17dd4bf@intel.com>
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: timer
Pid: 7995, comm: python Not tainted 2.6.32-573.26.1.el6.x86_64 #1
Call Trace:
[<ffffffff810eee02>] ? __setup_irq+0x382/0x3c0
[<ffffffffa00212a0>] ? uio_interrupt+0x0/0x48 [uio]
[<ffffffff810ef603>] ? request_threaded_irq+0x133/0x230
[<ffffffffa0021193>] ? __uio_register_device+0x553/0x610 [uio]
[<ffffffffa003797f>] ? igbuio_pci_probe+0x290/0x47a [igb_uio]
[<ffffffff81292c7a>] ? kobject_get+0x1a/0x30
[<ffffffff812b5e37>] ? local_pci_probe+0x17/0x20
[<ffffffff812b7021>] ? pci_device_probe+0x101/0x120
[<ffffffff813748e2>] ? driver_sysfs_add+0x62/0x90
[<ffffffff81374b8a>] ? driver_probe_device+0xaa/0x3a0
[<ffffffff81374f2b>] ? __driver_attach+0xab/0xb0
[<ffffffff81374e80>] ? __driver_attach+0x0/0xb0
[<ffffffff81373d74>] ? bus_for_each_dev+0x64/0x90
[<ffffffff8137481e>] ? driver_attach+0x1e/0x20
[<ffffffff812b73c7>] ? pci_add_dynid+0xc7/0xf0
[<ffffffff812b74c2>] ? store_new_id+0xd2/0x110
[<ffffffff81372d6c>] ? drv_attr_store+0x2c/0x30
[<ffffffff8120eb15>] ? sysfs_write_file+0xe5/0x170
[<ffffffff81192208>] ? vfs_write+0xb8/0x1a0
[<ffffffff811936f6>] ? fget_light_pos+0x16/0x50
[<ffffffff81192d41>] ? sys_write+0x51/0xb0
[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
igb_uio: probe of 0000:00:04.0 failed with error -16
IRQ handler type mismatch for IRQ 0
Regards,
Gregory
On Wed, Nov 15, 2017 at 5:44 PM, Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> 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
> > >
> >
> >
>
>
prev parent reply other threads:[~2017-11-15 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 22:38 [dpdk-stable] [PATCH] igb_uio: prevent reset for a list of devices Ferruh Yigit
2017-11-04 0:56 ` Mody, Rasesh
2017-11-06 18:48 ` [dpdk-stable] [PATCH v2] " Ferruh Yigit
2017-11-06 23:55 ` Thomas Monjalon
2017-11-07 11:50 ` [dpdk-stable] [dpdk-dev] " Chas Williams
2017-11-07 13:13 ` Stephen Hemminger
2017-11-07 18:14 ` Chas Williams
2017-11-09 17:20 ` [dpdk-stable] ugb_uio: r3.8xlarge bind failure Gregory Etelson
2017-11-10 1:42 ` Ferruh Yigit
2017-11-10 2:11 ` Ferruh Yigit
2017-11-10 6:36 ` Gregory Etelson
2017-11-15 15:44 ` Ferruh Yigit
2017-11-15 16:30 ` Gregory Etelson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO--2fH=oj73C+0Er6rnmKRxrXXMaqdheDo6+B-SSGOF0oqxew@mail.gmail.com' \
--to=gregory@weka.io \
--cc=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=george.prekas@epfl.ch \
--cc=harish.patil@cavium.com \
--cc=jianfeng.tan@intel.com \
--cc=jingjing.wu@intel.com \
--cc=lee.roberts@hpe.com \
--cc=rasesh.mody@cavium.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=shijith.thotton@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).