From: Harish Patil <harish.patil@qlogic.com>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: "huawie.xie@intel.com" <huawie.xie@intel.com>,
"yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] virtio PMD issue
Date: Fri, 15 Jul 2016 20:06:37 +0000 [thread overview]
Message-ID: <D3AE903E.531E2%harish.patil@qlogic.com> (raw)
In-Reply-To: <CAK3+h2y_j0cg=a1AU4OW7ReQyYfLWOxb6TAY6ff9+SCpcL4N4Q@mail.gmail.com>
>
>it is fixed in 16.07-rc2 that I checked
Great, thanks.
>
>Vincent
>
>On Fri, Jul 15, 2016 at 11:48 AM, Harish Patil <harish.patil@qlogic.com>
>wrote:
>> Hi Huawie/Yuanhan,
>> I encounter segfault issue in virtio PMD driver when I run any DPDK
>> application in the VM. The virtio devices should not have been probed in
>> the first place since they are not attached to igb_uio driver (and
>>managed
>> by kernel driver).
>>
>>
>> Network devices using DPDK-compatible driver
>> ============================================
>> 0000:00:09.0 'FastLinQ QL45000 Series 25GbE Controller' drv=igb_uio
>>unused=
>> 0000:00:0a.0 'FastLinQ QL45000 Series 25GbE Controller' drv=igb_uio
>>unused=
>>
>> Network devices using kernel driver
>> ===================================
>> 0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
>>
>>
>>
>> #0 0x00000000004e5392 in vtpci_init (dev=0xb61970, hw=0x7fff76146600)
>> at /home2/hpatil/dpdk/drivers/net/virtio/virtio_pci.c:653
>> #1 0x00000000004effc4 in eth_virtio_dev_init (eth_dev=0xacb7a0
>> <rte_eth_devices>)
>> at /home2/hpatil/dpdk/drivers/net/virtio/virtio_ethdev.c:1060
>> #2 0x00000000004b730f in rte_eth_dev_init ()
>> #3 0x00000000004cb940 in pci_probe_all_drivers ()
>> #4 0x00000000004cbe88 in rte_eal_pci_probe ()
>> #5 0x00000000004c0336 in rte_eal_init ()
>> #6 0x00000000004404e2 in main ()
>> (gdb) p dev->devargs
>> $1 = (struct rte_devargs *) 0x0
>>
>>
>> Looks like its a known issue based on a old thread:
>> http://dpdk.org/dev/patchwork/patch/12462/
>>
>> Do we know a fix now?
>>
>> Thanks,
>> harish
>>
>>
>>
>>
>
prev parent reply other threads:[~2016-07-15 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 18:48 Harish Patil
2016-07-15 19:55 ` Vincent Li
2016-07-15 20:06 ` Harish Patil [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=D3AE903E.531E2%harish.patil@qlogic.com \
--to=harish.patil@qlogic.com \
--cc=dev@dpdk.org \
--cc=huawie.xie@intel.com \
--cc=vincent.mc.li@gmail.com \
--cc=yuanhan.liu@linux.intel.com \
/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).