From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [dts] [Bug 670] Exception occurs when running nic_single_core_perf with latest DTS version
Date: Thu, 08 Apr 2021 14:37:21 +0000 [thread overview]
Message-ID: <bug-670-433-0OEL5dFsj8@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-670-433@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=670
dliu (dliu@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dliu@iol.unh.edu
--- Comment #3 from dliu (dliu@iol.unh.edu) ---
Hi Ali,
I was testing our Mellanox machine with Trex V2.88 and recent dts
But because we have an older driver version, it was not able to start Trex.
pktgen: ssh root@127.0.0.1
pktgen: cd /opt/v2.88;./t-rex-64 -i --cfg
/etc/trex_cfg_cx4lx25g.yaml -c 7
Exception happened in [cd /opt/v2.88;./t-rex-64 -i --cfg
/etc/trex_cfg_cx4lx25g.yaml -c 7] and output is [ Warning: Mellanox NICs were
tested only with RedHat/CentOS 7.9
Correct usage with other Linux distributions is not guaranteed.
Installed OFED version is 'b'MLNX_OFED_LINUX-5.0-2.1.8.0 (OFED-5.0-2.1.8):'',
should be at least '5.2' and up.
ERROR encountered while configuring TRex system]
dts: TIMEOUT on cd /opt/v2.88;./t-rex-64 -i --cfg
/etc/trex_cfg_cx4lx25g.yaml -c 7
tester: pkill -f _t-rex-64
Traceback (most recent call last):
File "/home/jenkins/dts_per_test/framework/dts.py", line 342, in
dts_crbs_init
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-04-08 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 12:22 [dts] [Bug 670] Exception occurs with " bugzilla
2021-04-08 12:24 ` bugzilla
2021-04-08 12:28 ` bugzilla
2021-04-08 12:29 ` [dts] [Bug 670] Exception occurs when " bugzilla
2021-04-08 14:37 ` bugzilla [this message]
2021-04-08 15:23 ` bugzilla
2021-04-12 1:54 ` bugzilla
2021-04-14 14:29 ` bugzilla
2021-05-06 14:08 ` bugzilla
2021-06-17 13:08 ` bugzilla
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-670-433-0OEL5dFsj8@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dts@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).