* [dpdk-users] Example app link_status_interrupt: interfaces come not up
@ 2018-04-20 10:05 Martin Trommer
0 siblings, 0 replies; only message in thread
From: Martin Trommer @ 2018-04-20 10:05 UTC (permalink / raw)
To: users
Hello DPDK users,
If I start the DPDK sample application "link_status_interrupt" the interface states will not change. It stays DOWN. App is exited by sending Signal SIGINT.
A second start of "./link_status_interrupt" will show the interface states as UP.
A third start will also show the interface states as UP.
Here my command:
./link_status_interrupt -w 0000:18:00.2 -w 0000:18:00.3 -l 0-2 -- -q 2 -p 3
0000:18:00.2 and 0000:18:00.3 are wired with each other.
I use a X710 on board chip with 4 interfaces (0000:18:00.0 - 0000:18:00.3).
DPDK 18.02 is used.
What can I do that the interfaces will come UP in the first run ?
Thanks in advance,
Martin
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-20 10:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-20 10:05 [dpdk-users] Example app link_status_interrupt: interfaces come not up Martin Trommer
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).