Bug 2211195

Summary:	[RHEL-8.9] ucx_perftest in UCX produces core file in client host when tested on MLX5 IB devices
Product:	Red Hat Enterprise Linux 8	Reporter:	Brian Chae <bchae>
Component:	ucx	Assignee:	Nobody <nobody>
Status:	CLOSED MIGRATED	QA Contact:	Infiniband QE <infiniband-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.9	CC:	rdma-dev-team
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 13:43:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian Chae 2023-05-30 16:49:37 UTC

Description of problem:

After "ucx_perftest" tests, RDMA client was left with SIG 6 core file. This happened the UCX was tested on MLX5 IB devices.

TIME                            PID   UID   GID SIG COREFILE  EXE

Sat 2023-05-27 14:05:06 EDT  331688     0     0   6 none      /usr/bin/ucx_perftest
Sat 2023-05-27 14:08:42 EDT  331781     0     0   6 none      /usr/bin/ucx_perftest
Sat 2023-05-27 14:11:08 EDT  331866     0     0   6 none      /usr/bin/ucx_perftest
Sat 2023-05-27 14:14:44 EDT  331960     0     0   6 none      /usr/bin/ucx_perftest
Sat 2023-05-27 14:17:10 EDT  332047     0     0   6 none      /usr/bin/ucx_perftest




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

Clients: rdma-perf-03
Servers: rdma-perf-02

DISTRO=RHEL-8.9.0-20230521.41

+ [23-05-27 14:03:46] cat /etc/redhat-release
Red Hat Enterprise Linux release 8.9 Beta (Ootpa)

+ [23-05-27 14:03:46] uname -a
Linux rdma-perf-03.rdma.lab.eng.rdu2.redhat.com 4.18.0-492.el8.x86_64 #1 SMP Tue May 9 14:50:21 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux

+ [23-05-27 14:03:46] cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-492.el8.x86_64 root=UUID=ba31a4b2-48e9-406e-82c0-86137253e7c5 ro intel_idle.max_cstate=0 processor.max_cstate=0 intel_iommu=on iommu=on console=tty0 rd_NO_PLYMOUTH intel_idle.max_cstate=0 intremap=no_x2apic_optout processor.max_cstate=0 reboot=acpi crashkernel=auto resume=UUID=6342dea0-23ae-4c1d-8132-4d6e2037fa0e console=ttyS1,115200n81

+ [23-05-27 14:03:46] rpm -q rdma-core linux-firmware
rdma-core-44.0-2.el8.1.x86_64
linux-firmware-20230515-115.gitd1962891.el8.noarch

+ [23-05-27 14:03:46] tail /sys/class/infiniband/mlx5_0/fw_ver /sys/class/infiniband/mlx5_1/fw_ver
==> /sys/class/infiniband/mlx5_0/fw_ver <==
16.33.1048

==> /sys/class/infiniband/mlx5_1/fw_ver <==
16.33.1048

+ [23-05-27 14:03:46] lspci
+ [23-05-27 14:03:46] grep -i -e ethernet -e infiniband -e omni -e ConnectX
03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.2 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.3 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
07:00.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5]
07:00.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5]



How reproducible:
100%

Steps to Reproduce:

Please, refer to the following beaker test logs:

https://beaker.engineering.redhat.com/jobs/7908288 

https://beaker-archive.hosts.prod.psi.bos.redhat.com/beaker-logs/2023/05/79082/7908288/13996201/161005246/752813761/resultoutputfile.log


1.
2.
3.

Actual results:


Expected results:

No core files produced after UCX tests




Additional info:

Comment 1 RHEL Program Management 2023-09-21 13:39:50 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 13:43:39 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.