Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-6194

[RHEL9.1] all mvapich2 benchmarks fail with "Caught error: Segmentation fault" on MLX5 CIB device

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • None
    • None
    • rhel-net-drivers
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • 57,005

      Description of problem:

      All benchmarks fail with Segmentation fault as the following when mvapich2 tested on MLX5 CIB devices.

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

      Clients: rdma-qe-07
      Servers: rdma-qe-06

      DISTRO=RHEL-9.1.0-20220609.0

      + [22-06-09 06:40:02] cat /etc/redhat-release
      Red Hat Enterprise Linux release 9.1 Beta (Plow)

      + [22-06-09 06:40:02] uname -a
      Linux rdma-qe-07.rdma.lab.eng.rdu2.redhat.com 5.14.0-106.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jun 7 07:22:29 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux

      + [22-06-09 06:40:02] cat /proc/cmdline
      BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-106.el9.x86_64 root=/dev/mapper/rhel_rdma-qe07-root ro intel_idle.max_cstate=0 intremap=no_x2apic_optout processor.max_cstate=0 console=tty0 rd_NO_PLYMOUTH crashkernel=1G-4G:192M,4G-64G:256M,64G:512M resume=/dev/mapper/rhel_rdma-qe-07-swap rd.lvm.lv=rhel_rdma-qe-07/root rd.lvm.lv=rhel_rdma-qe-07/swap console=ttyS1,115200n81

      + [22-06-09 06:40:02] rpm -q rdma-core linux-firmware
      rdma-core-37.2-1.el9.x86_64
      linux-firmware-20220509-126.el9.noarch

      + [22-06-09 06:40:02] tail /sys/class/infiniband/mlx5_0/fw_ver
      10.16.1200
      + [22-06-09 06:40:02] lspci
      + [22-06-09 06:40:02] grep -i -e ethernet -e infiniband -e omni -e ConnectX
      03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5717 Gigabit Ethernet PCIe (rev 10)
      03:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5717 Gigabit Ethernet PCIe (rev 10)
      05:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]

      Installed:
      mpitests-mvapich2-5.8-1.el9.x86_64 mvapich2-2.3.6-3.el9.x86_64

      How reproducible:

      100%

      Steps to Reproduce:
      1. bring up the RDMA hosts mentioned above with RHEL9.1 build
      2. set up RDMA hosts for mvapich2 benchamrk tests
      3. run one of the mvapich2 benchmark with "mpirun" command, as the following:

      timeout --preserve-status --kill-after=5m 3m mpirun -hostfile /root/hfile_one_core -np 2 mpitests-IMB-MPI1 PingPong -time 1.5

      Actual results:

      [rdma-qe-06.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][rdma_find_network_type] Warning: Detected active HCAs in different subnets (mlx5_1 in subnet 1 and mlx5_0 in subnet 3). This can cause hangs. Plese use MV2_IBA_HCA to select appropriate HCAs or force rail sharing.
      [rdma-qe-06.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][rdma_param_handle_heterogeneity] All nodes involved in the job were detected to be homogeneous in terms of processors and interconnects. Setting MV2_HOMOGENEOUS_CLUSTER=1 can improve job startup performance on such systems. The following link has more details on enhancing job startup performance. http://mvapich.cse.ohio-state.edu/performance/job-startup/.
      [rdma-qe-06.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][rdma_param_handle_heterogeneity] To suppress this warning, please set MV2_SUPPRESS_JOB_STARTUP_PERFORMANCE_WARNING to 1
      #----------------------------------------------------------------

      1. Intel(R) MPI Benchmarks 2021.3, MPI-1 part
        #----------------------------------------------------------------
      2. Date : Thu Jun 9 06:40:13 2022
      3. Machine : x86_64
      4. System : Linux
      5. Release : 5.14.0-106.el9.x86_64
      6. Version : #1 SMP PREEMPT_DYNAMIC Tue Jun 7 07:22:29 EDT 2022
      7. MPI Version : 3.1
      8. MPI Thread Environment:
      1. Calling sequence was:
      1. mpitests-IMB-MPI1 PingPong -time 1.5
      1. Minimum message length in bytes: 0
      2. Maximum message length in bytes: 4194304
        #
      3. MPI_Datatype : MPI_BYTE
      4. MPI_Datatype for reductions : MPI_FLOAT
      5. MPI_Op : MPI_SUM
      1. List of Benchmarks to run:
      1. PingPong
        [rdma-qe-06.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][error_sighandler] Caught error: Segmentation fault (signal 11)
        [rdma-qe-07.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][error_sighandler] Caught error: Segmentation fault (signal 11) <<<=====================

      ===================================================================================
      = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
      = PID 30228 RUNNING AT 172.31.0.7
      = EXIT CODE: 139
      = CLEANING UP REMAINING PROCESSES
      = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
      ===================================================================================
      [proxy:0:0@rdma-qe-06.rdma.lab.eng.rdu2.redhat.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:911): assert (!closed) failed
      [proxy:0:0@rdma-qe-06.rdma.lab.eng.rdu2.redhat.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
      [proxy:0:0@rdma-qe-06.rdma.lab.eng.rdu2.redhat.com] main (pm/pmiserv/pmip.c:202): demux engine error waiting for event
      YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
      This typically refers to a problem with your application.
      Please see the FAQ page for debugging suggestions
      + [22-06-09 06:40:13] __MPI_check_result 139 mpitests-mvapich2 IMB-MPI1 PingPong mpirun /root/hfile_one_core

      Expected results:

      Normal execution of benchmarks with stats

      Additional info:

              kheib Kamal Heib
              bchae Brian Chae (Inactive)
              Kamal Heib Kamal Heib
              infiniband-qe infiniband-qe infiniband-qe infiniband-qe
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: