From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 475] failure in `EAL flags autotest`
Date: Thu, 14 May 2020 02:27:33 +0000 [thread overview]
Message-ID: <bug-475-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=475
Bug ID: 475
Summary: failure in `EAL flags autotest`
Product: DPDK
Version: 20.05
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK:20.05-rc2
Linux:4.15.0-99-generic
GCC: Ubuntu 7.5.0-3ubuntu1~18.04
Distribution: Ubuntu 18.04.4 LTS
logs
```
eal_flags_autotest
eal_flags_autotest
Error converting name fd 0 .:
Error converting name fd 0 ..:
Running binary with
argv[]:'/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test'
'--file-prefix=test2' '--proc-type=secondary'
EAL: Detected 88 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/test2/mp_socket_36971_6e46f8e2994910
EAL: failed to send to (/var/run/dpdk/test2/mp_socket) due to No such file or
directory
EAL: Fail to send request /var/run/dpdk/test2/mp_socket:bus_vdev_mp
vdev_scan(): Failed to request vdev from primary
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
No telemetry legacy support - No legacy callbacks, legacy socket not created
Error converting name fd 0 .:
Error converting name fd 0 ..:
Running binary with
argv[]:'/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test'
'--file-prefix=test2' '--proc-type=secondary' '-c'
/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test:
option requires an argument -- 'c'
EAL: Detected 88 lcore(s)
EAL: Detected 2 NUMA nodes
/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test:
option requires an argument -- 'c'
```
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-05-14 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-475-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.