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 2211195 - [RHEL-8.9] ucx_perftest in UCX produces core file in client host when tested on MLX5 IB devices
Summary: [RHEL-8.9] ucx_perftest in UCX produces core file in client host when tested ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ucx
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nobody
QA Contact: Infiniband QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-30 16:49 UTC by Brian Chae
Modified: 2023-09-21 13:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 13:43:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-6077 0 None Migrated None 2023-09-21 13:43:30 UTC
Red Hat Issue Tracker RHELPLAN-158602 0 None None None 2023-05-30 16:51:51 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.