From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Thomas F Herbert <therbert@redhat.com>
Cc: dev@dpdk.org, "Gray, Mark D" <mark.d.gray@intel.com>,
Tim Rozet <trozet@redhat.com>
Subject: Re: [dpdk-dev] segfault in vt_pci_init
Date: Wed, 22 Jun 2016 15:39:10 +0200 [thread overview]
Message-ID: <33332591.NU01Sd09qa@xps13> (raw)
In-Reply-To: <576A8424.7080000@redhat.com>
2016-06-22 14:27, Thomas F Herbert:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000616172 in vtpci_init (dev=0xbfb0f0, hw=0x7fffd57d0700,
> dev_flags=0x7fffffffdf9c)
> at /home/heat-admin/dpdk/drivers/net/virtio/virtio_pci.c:722
> 722 dev->devargs->type != RTE_DEVTYPE_WHITELISTED_PCI) {
Please could you check with the current HEAD?
Maybe this commit can fix your issue:
http://dpdk.org/commit/7e40200c56
next prev parent reply other threads:[~2016-06-22 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 12:27 Thomas F Herbert
2016-06-22 13:39 ` Thomas Monjalon [this message]
2016-06-22 14:25 ` Thomas F Herbert
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=33332591.NU01Sd09qa@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=mark.d.gray@intel.com \
--cc=therbert@redhat.com \
--cc=trozet@redhat.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).