Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Filip Krakowski <krakowski@hhu.de>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: ibv_rc_pingpong fails to create a completion queue
Date: Tue, 23 Feb 2021 10:56:13 +0200	[thread overview]
Message-ID: <YDTDLd8cvGUgtkqb@unreal> (raw)
In-Reply-To: <CAD=hENcBOO3KfH4wHoz1GBz9LPVZ5BOnoyPq8MMtbhB0DA=F5w@mail.gmail.com>

On Tue, Feb 23, 2021 at 11:08:18AM +0800, Zhu Yanjun wrote:
> On Tue, Feb 23, 2021 at 12:21 AM Filip Krakowski <krakowski@hhu.de> wrote:
> >
> > Hi,
> >
> > whenever I try to test a reliable connection using "ibv_rc_pingpong -d
> > mlx5_0"
>
> ibv_rc_pingpong -d rxe0 -g 1 > /dev/null &
>
> ibv_rc_pingpong -d rxe0 -g 1 192.168.1.2
>
> I made tests with the above. It can work well.
>
> Normally "-g" is needed.

"-g" is needed because you are running RoCE, while Filip is running IB.

>
> Before directly using mlx5, please make tests with softroce firstly.

Are you sure that RXE works in 4.18.0-151.el8.x86_64 kernel?

>
> Zhu Yanjun
>
>  to start the server side the test immediately stops with
> > "Couldn't create CQ". Since I couldn't find a solution for this problem
> > in one week I would like to ask if someone has encountered this error
> > before or knows a way of troubleshooting it. Just to be sure I updated
> > the controller to its latest firmware (16.29.2002) today, but the error
> > remained the same.
> >
> > System Information
> > ====
> >
> >      * CentOS Linux release 8.1.1911 (Core)
> >      * Linux 4.18.0-151.el8.x86_64
> >      * ConnectX-5 (MCX555A-ECA)
> >
> >
> > Installed Packages
> > ====
> >
> >      * rdma-core-32.0-4.el8.x86_64
> >      * libibverbs-32.0-4.el8.x86_64
> >
> >
> > Loaded Kernel Modules (lsmod | grep -E 'rdma|mlx')
> > ====
> >
> >      rpcrdma               274432  0
> >      sunrpc                454656  22
> > rpcrdma,nfsv4,auth_rpcgss,lockd,nfsv3,rpcsec_gss_krb5,nfs_acl,nfs
> >      rdma_ucm               32768  0
> >      rdma_cm                69632  5
> > rpcrdma,ib_srpt,ib_iser,ib_isert,rdma_ucm
> >      iw_cm                  53248  1 rdma_cm
> >      ib_cm                  57344  3 rdma_cm,ib_ipoib,ib_srpt
> >      mlx5_ib               327680  0
> >      ib_uverbs             147456  3 i40iw,rdma_ucm,mlx5_ib
> >      ib_core               356352  14
> > rdma_cm,ib_ipoib,rpcrdma,ib_srpt,iw_cm,ib_iser,ib_umad,ib_isert,i40iw,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
> >      mlx5_core             798720  1 mlx5_ib
> >      mlxfw                  24576  1 mlx5_core
> >
> >
> >
> > Infiniband Device Info (ibv_devinfo)
> > ====
> >
> >      hca_id:    i40iw0
> >          transport:            iWARP (1)
> >          fw_ver:                0.2
> >          node_guid:            3cec:ef0d:51c3:0000
> >          sys_image_guid:            3cec:ef0d:51c3:0000
> >          vendor_id:            0x8086
> >          vendor_part_id:            14290
> >          hw_ver:                0x0
> >          board_id:            I40IW Board ID
> >          phys_port_cnt:            1
> >              port:    1
> >                  state:            PORT_DOWN (1)
> >                  max_mtu:        4096 (5)
> >                  active_mtu:        1024 (3)
> >                  sm_lid:            0
> >                  port_lid:        1
> >                  port_lmc:        0x00
> >                  link_layer:        Ethernet
> >
> >      hca_id:    i40iw1
> >          transport:            iWARP (1)
> >          fw_ver:                0.2
> >          node_guid:            3cec:ef0d:51c2:0000
> >          sys_image_guid:            3cec:ef0d:51c2:0000
> >          vendor_id:            0x8086
> >          vendor_part_id:            14290
> >          hw_ver:                0x0
> >          board_id:            I40IW Board ID
> >          phys_port_cnt:            1
> >              port:    1
> >                  state:            PORT_ACTIVE (4)
> >                  max_mtu:        4096 (5)
> >                  active_mtu:        1024 (3)
> >                  sm_lid:            0
> >                  port_lid:        1
> >                  port_lmc:        0x00
> >                  link_layer:        Ethernet
> >
> >      hca_id:    mlx5_0
> >          transport:            InfiniBand (0)
> >          fw_ver:                16.29.2002
> >          node_guid:            0c42:a103:0054:74ca
> >          sys_image_guid:            0c42:a103:0054:74ca
> >          vendor_id:            0x02c9
> >          vendor_part_id:            4119
> >          hw_ver:                0x0
> >          board_id:            MT_0000000010
> >          phys_port_cnt:            1
> >              port:    1
> >                  state:            PORT_ACTIVE (4)
> >                  max_mtu:        4096 (5)
> >                  active_mtu:        4096 (5)
> >                  sm_lid:            8
> >                  port_lid:        196
> >                  port_lmc:        0x00
> >                  link_layer:        InfiniBand
> >
> >
> > Best regards
> > Filip

  reply	other threads:[~2021-02-23  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 16:19 ibv_rc_pingpong fails to create a completion queue Filip Krakowski
2021-02-23  3:08 ` Zhu Yanjun
2021-02-23  8:56   ` Leon Romanovsky [this message]
2021-02-23  9:50     ` Zhu Yanjun
2021-02-23 13:45       ` Filip Krakowski
2021-02-24 10:27         ` Zhu Yanjun

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=YDTDLd8cvGUgtkqb@unreal \
    --to=leon@kernel.org \
    --cc=krakowski@hhu.de \
    --cc=linux-rdma@vger.kernel.org \
    --cc=zyjzyj2000@gmail.com \
    /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