From: Thomas Monjalon <thomas@monjalon.net>
To: sys_stv@intel.com
Cc: test-report@dpdk.org
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (56/60)
Date: Fri, 27 Oct 2017 09:59:40 +0200 [thread overview]
Message-ID: <2487221.MH4jkIm4I7@xps> (raw)
In-Reply-To: <419c8d$um820p@orsmga003.jf.intel.com>
About old kernels, now you need to disable expicitly VFIO in DPDK config.
27/10/2017 05:19, sys_stv@intel.com:
>
> Failure #1
> UBT124_64 / Linux 3.8.0-29 / GCC 4.6.3
> Config: x86_64-native-linuxapp-gcc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> SYMLINK-FILE include/exec-env/rte_kni_common.hIn file included from DPDK/lib/librte_eal/linuxapp/eal/eal.c:79:0:
> DPDK/x86_64-native-linuxapp-gcc/include/rte_vfio.h:37:24: fatal error: linux/vfio.h: No such file or directory
> compilation terminated.
>
> Failure #2
> UBT124_64 / Linux 3.8.0-29 / ICC 16.0.2
> Config: x86_64-native-linuxapp-icc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> SYMLINK-FILE include/exec-env/rte_kni_common.hIn file included from DPDK/lib/librte_eal/linuxapp/eal/eal.c:79:0:
> DPDK/x86_64-native-linuxapp-gcc/include/rte_vfio.h:37:24: fatal error: linux/vfio.h: No such file or directory
> compilation terminated.
next prev parent reply other threads:[~2017-10-27 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 3:19 sys_stv
2017-10-27 7:59 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 20:13 sys_stv
2017-10-30 20:27 sys_stv
2017-10-29 20:26 sys_stv
2017-10-27 20:28 sys_stv
2017-07-05 20:24 sys_stv
2017-07-05 3:27 sys_stv
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=2487221.MH4jkIm4I7@xps \
--to=thomas@monjalon.net \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
/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).