2148782 – [RHEL8.8] libvma test fails consistently on "sockperf pingpong multicast pkey/vlan" when tested on MLX4 IB0 device

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2148782 - [RHEL8.8] libvma test fails consistently on "sockperf pingpong multicast pkey/vlan" when tested on MLX4 IB0 device

Summary: [RHEL8.8] libvma test fails consistently on "sockperf pingpong multicast pkey...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	libvma
Sub Component:
Version:	8.8
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Kamal Heib
QA Contact:	Infiniband QE
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-11-27 22:30 UTC by Brian Chae
Modified:	2023-09-21 14:28 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-21 14:28:18 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-6133	0	None	Migrated	None	2023-09-21 14:28:22 UTC
Red Hat Issue Tracker	RHELPLAN-140555	0	None	None	None	2022-11-27 23:00:26 UTC

Description Brian Chae 2022-11-27 22:30:28 UTC

Description of problem:

"sockperf pingpong multicast pkey/vlan" test case consistently fails when libvma is tested on MLX4 IB0 devices.

vma test results on rdma-virt-00/rdma-virt-01 & Beaker job J:7282087:
4.18.0-438.el8.x86_64, rdma-core-41.0-1.el8, mlx4, ib0, ConnectX-3 Pro & mlx4_0
    Result | Status | Test
  ---------+--------+------------------------------------
      PASS |      0 | sockperf pingpong multicast
      PASS |      0 | sockperf throughput multicast
      PASS |      0 | sockperf throughput unicast
      PASS |      0 | sockperf pingpong unicast
      PASS |      0 | sockperf (100 sockets) pingpong multicast
      PASS |      0 | sockperf (100 sockets) pingpong unicast
      FAIL |      1 | sockperf pingpong multicast pkey/vlan <<<============
      PASS |      0 | sockperf pingpong unicast pkey/vlan
Checking for failures and known issues:
  sockperf pingpong multicast pkey/vlan is NOT a known issue on any environment - consider filing a BZ

+++++++++++++++++++++++++

This is a regression where, with RHEL-8.7.0, the same test passes.
vma test results on rdma-virt-00/rdma-virt-01 & Beaker job J:7282212:
4.18.0-425.3.1.el8.x86_64, rdma-core-41.0-1.el8, mlx4, ib0, ConnectX-3 Pro & mlx4_0
    Result | Status | Test
  ---------+--------+------------------------------------
      PASS |      0 | sockperf pingpong multicast
      PASS |      0 | sockperf throughput multicast
      PASS |      0 | sockperf throughput unicast
      PASS |      0 | sockperf pingpong unicast
      PASS |      0 | sockperf (100 sockets) pingpong multicast
      PASS |      0 | sockperf (100 sockets) pingpong unicast
      PASS |      0 | sockperf pingpong multicast pkey/vlan <<<=====
      PASS |      0 | sockperf pingpong unicast pkey/vlan
Checking for failures and known issues:
  no test failures



Version-Release number of selected component (if applicable):

Clients: rdma-virt-01
Servers: rdma-virt-00

DISTRO=RHEL-8.8.0-20221120.2

+ [22-11-27 12:50:17] cat /etc/redhat-release
Red Hat Enterprise Linux release 8.8 Beta (Ootpa)

+ [22-11-27 12:50:17] uname -a
Linux rdma-virt-01.rdma.lab.eng.rdu2.redhat.com 4.18.0-438.el8.x86_64 #1 SMP Mon Nov 14 13:08:07 EST 2022 x86_64 x86_64 x86_64 GNU/Linux

+ [22-11-27 12:50:17] cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-438.el8.x86_64 root=UUID=7a33441c-1f35-4485-a8ce-fb7f97d8ec9b ro intel_idle.max_cstate=0 processor.max_cstate=0 intel_iommu=on iommu=on console=tty0 rd_NO_PLYMOUTH crashkernel=auto resume=UUID=38129101-96b6-4039-9d07-de4355860d19 console=ttyS1,115200n81

+ [22-11-27 12:50:17] rpm -q rdma-core linux-firmware
rdma-core-41.0-1.el8.x86_64
linux-firmware-20220726-110.git150864a4.el8.noarch

+ [22-11-27 12:50:17] tail /sys/class/infiniband/mlx4_0/fw_ver /sys/class/infiniband/mlx4_1/fw_ver
==> /sys/class/infiniband/mlx4_0/fw_ver <==
2.42.5000

==> /sys/class/infiniband/mlx4_1/fw_ver <==
2.42.5000

+ [22-11-27 12:50:17] lspci
+ [22-11-27 12:50:17] grep -i -e ethernet -e infiniband -e omni -e ConnectX
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
02:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
03:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
04:00.0 Network controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro]
04:00.1 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.2 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.3 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.4 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.5 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.6 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
04:00.7 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
06:00.0 Network controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro]


+ [22-11-27 12:50:18] rpm -q libvma
libvma-9.6.4-1.el8.x86_64



How reproducible:

100%

Steps to Reproduce:

On both server and client hosts:

+ [22-11-27 12:58:15] export SERVER_IP2=172.31.2.200
+ [22-11-27 12:58:15] SERVER_IP2=172.31.2.200

1. Get both RDMA server & client hosts ready for libvma test with current sockperf, with RHEL-8.8 build as specified above on MLX4 IB0 devices
2. On server host, issue the following commands

LD_PRELOAD=libvma.so
timeout --preserve-status --kill-after=5m 3m sockperf server -i 172.31.2.200

3. On the client hosts, issue the following command

LD_PRELOAD=libvma.so
timeout --preserve-status --kill-after=5m 3m sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472


Actual results:

[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: date ++ [%y-%m-%d %H:%M:%S]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m+ [22-11-27 13:00:53] LD_PRELOAD=libvma.so
[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: date ++ [%y-%m-%d %H:%M:%S]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m+ [22-11-27 13:00:53] timeout --preserve-status --kill-after=5m 3m sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: timeout --preserve-status --kill-after=5m 3m sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0msockperf: [2;35m== version #3.10-0.git5ebd327da983 == [0m
sockperf[CLIENT] send on:sockperf: using recvfrom() to block on socket(s)

[ 0] IP = 172.31.2.200    PORT = 11111 # UDP
sockperf: Warmup stage (sending a few dummy messages)...
sockperf: Starting test...
sockperf: Test end (interrupted by timer)
sockperf: Test ended
sockperf: No messages were received from the server. Is the server down?
+ [22-11-27 13:01:07] result=0
+ [22-11-27 13:01:07] '[' 0 -ne 0 ']'
+ [22-11-27 13:01:07] grep -qi -e ' error ' -e 'no messages were received' /tmp/vma.txt
+ [22-11-27 13:01:07] return 1




Expected results: On RHEL-8.7.0, the above same testcase result look like the following:


[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: date ++ [%y-%m-%d %H:%M:%S]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m+ [22-11-27 16:42:52] LD_PRELOAD=libvma.so
[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: date ++ [%y-%m-%d %H:%M:%S]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m+ [22-11-27 16:42:52] timeout --preserve-status --kill-after=5m 3m sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: timeout --preserve-status --kill-after=5m 3m sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: VMA_VERSION: 9.6.4-1 Release built on Aug 17 2022 14:23:56
[0m[0m VMA INFO: Cmd Line: sockperf pp -i 172.31.2.200 -t 10 --msg-size=1472
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0m[0m VMA INFO: Log Level                      INFO                       [VMA_TRACELEVEL]
[0m[0m VMA INFO: ---------------------------------------------------------------------------
[0msockperf: [2;35m== version #3.10-0.git5ebd327da983 == [0m
sockperf[CLIENT] send on:sockperf: using recvfrom() to block on socket(s)

[ 0] IP = 172.31.2.200    PORT = 11111 # UDP
sockperf: Warmup stage (sending a few dummy messages)...
sockperf: Starting test...
sockperf: Test end (interrupted by timer)
sockperf: Test ended
sockperf: [Total Run] RunTime=10.000 sec; Warm up time=400 msec; SentMessages=1785444; ReceivedMessages=1785443
sockperf: ========= Printing statistics for Server No: 0
sockperf: [Valid Duration] RunTime=9.550 sec; SentMessages=1711702; ReceivedMessages=1711702
sockperf: [2;35m====> avg-latency=2.772 (std-dev=0.286, mean-ad=0.081, median-ad=0.036, siqr=0.028, cv=0.103, std-error=0.000, 99.0% ci=[2.771, 2.773])[0m
sockperf: # dropped messages = 0; # duplicated messages = 0; # out-of-order messages = 0
sockperf: Summary: Latency is 2.772 usec
sockperf: [2;35mTotal 1711702 observations[0m; each percentile contains 17117.02 observations
sockperf: ---> <MAX> observation =   81.937
sockperf: ---> percentile 99.999 =   55.007
sockperf: ---> percentile 99.990 =    4.831
sockperf: ---> percentile 99.900 =    4.301
sockperf: ---> percentile 99.000 =    3.303
sockperf: ---> percentile 90.000 =    2.901
sockperf: ---> percentile 75.000 =    2.763
sockperf: ---> percentile 50.000 =    2.728
sockperf: ---> percentile 25.000 =    2.706
sockperf: ---> <MIN> observation =    2.621
+ [22-11-27 16:43:06] result=0
+ [22-11-27 16:43:06] '[' 0 -ne 0 ']'
+ [22-11-27 16:43:06] grep -qi -e ' error ' -e 'no messages were received' /tmp/vma.txt
+ [22-11-27 16:43:06] return 0
+ [22-11-27 16:43:06] RQA_check_result -r 0 -t 'sockperf pingpong multicast pkey/vlan'



Additional info:

Comment 1 RHEL Program Management 2023-09-21 14:27:57 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 14:28:18 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.