linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yanjun <zyjzyj2000@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	Bob Pearson <rpearsonhpe@gmail.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: RXE status in the upstream rping using rxe
Date: Mon, 23 Aug 2021 15:53:02 +0800	[thread overview]
Message-ID: <CAD=hENdad8RGTLo82UBf3k+koQVX1oHSXMz6HfRvUxrL4dttsw@mail.gmail.com> (raw)
In-Reply-To: <YQmF9506lsmeaOBZ@unreal>

On Wed, Aug 4, 2021 at 2:07 AM Leon Romanovsky <leon@kernel.org> wrote:
>
> Hi,
>
> Can you please help me to understand the RXE status in the upstream?

Hi, all

On the Ubuntu 20.04, kernel: 5.4.0-80, with the latest rdma-core,

"
root@xxx:~/rdma-core# cat /etc/issue
Ubuntu 20.04.2 LTS \n \l
root@xxx:~/rdma-core# uname -a
Linux 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
root@xxx:~/rdma-core# git log -1 --oneline
206a0cfd (HEAD -> master, origin/master, origin/HEAD) Merge pull
request #1047 from yishaih/mlx5_misc
"

Run run_tests.py, I got the following errors.

Not sure if it is a problem. Please comment on it.

It is easy to reproduce on Ubuntu 20.04 + 5.4.0-80.

"
.............sssssssss..FFF........sssssssssssssss.sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss.ssssssssssssssssssssssssss....s...ss..........s....s..s.......ssReceived
the following exceptions: {'active': BrokenBarrierError()}
EReceived the following exceptions: {'active': BrokenBarrierError()}
E........ss
======================================================================
ERROR: test_rdmacm_async_ex_multicast_traffic (tests.test_rdmacm.CMTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rdma-core/tests/utils.py", line 976, in inner
    return func(instance)
  File "/root/rdma-core/tests/test_rdmacm.py", line 42, in
test_rdmacm_async_ex_multicast_traffic
    self.two_nodes_rdmacm_traffic(CMAsyncConnection,
  File "/root/rdma-core/tests/base.py", line 368, in two_nodes_rdmacm_traffic
    raise(res)
threading.BrokenBarrierError

======================================================================
ERROR: test_rdmacm_async_multicast_traffic (tests.test_rdmacm.CMTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rdma-core/tests/utils.py", line 976, in inner
    return func(instance)
  File "/root/rdma-core/tests/test_rdmacm.py", line 36, in
test_rdmacm_async_multicast_traffic
    self.two_nodes_rdmacm_traffic(CMAsyncConnection,
  File "/root/rdma-core/tests/base.py", line 368, in two_nodes_rdmacm_traffic
    raise(res)
threading.BrokenBarrierError

======================================================================
FAIL: test_phys_port_cnt_ex (tests.test_device.DeviceTest)
Test phys_port_cnt_ex
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rdma-core/tests/test_device.py", line 222, in
test_phys_port_cnt_ex
    self.assertEqual(phys_port_cnt, phys_port_cnt_ex,
AssertionError: 1 != 0 : phys_port_cnt_ex and phys_port_cnt should be
equal if number of ports is less than 256

======================================================================
FAIL: test_query_device (tests.test_device.DeviceTest)
Test ibv_query_device()
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rdma-core/tests/test_device.py", line 63, in test_query_device
    self.verify_device_attr(attr, dev)
  File "/root/rdma-core/tests/test_device.py", line 187, in verify_device_attr
    assert attr.vendor_id != 0
AssertionError

======================================================================
FAIL: test_query_device_ex (tests.test_device.DeviceTest)
Test ibv_query_device_ex()
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/rdma-core/tests/test_device.py", line 206, in test_query_device_ex
    self.verify_device_attr(attr_ex.orig_attr, dev)
  File "/root/rdma-core/tests/test_device.py", line 187, in verify_device_attr
    assert attr.vendor_id != 0
AssertionError

----------------------------------------------------------------------
Ran 205 tests in 40.112s

FAILED (failures=3, errors=2, skipped=137)
Traceback (most recent call last):
  File "device.pyx", line 170, in pyverbs.device.Context.close
AttributeError: 'NoneType' object has no attribute 'debug'
Exception ignored in: 'pyverbs.device.Context.__dealloc__'
Traceback (most recent call last):
  File "device.pyx", line 170, in pyverbs.device.Context.close
AttributeError: 'NoneType' object has no attribute 'debug'
"


>
> Does we still have crashes/interop issues/e.t.c?
>
> Latest commit is:
> 20da44dfe8ef ("RDMA/mlx5: Drop in-driver verbs object creations")
>
> Thanks

      parent reply	other threads:[~2021-08-23  7:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 18:07 RXE status in the upstream rping using rxe Leon Romanovsky
2021-08-04  1:01 ` Zhu Yanjun
2021-08-04  1:09   ` Zhu Yanjun
2021-08-04  5:41     ` Leon Romanovsky
2021-08-04  9:05       ` Zhu Yanjun
2021-08-06  2:37         ` Olga Kornievskaia
2021-08-17  2:28           ` Zhu Yanjun
2021-08-18  6:43             ` yangx.jy
2021-08-18  7:20               ` Zhu Yanjun
2021-08-18  7:44                 ` yangx.jy
2021-08-18  8:28                   ` Zhu Yanjun
2021-08-18 14:33                     ` yangx.jy
2021-08-20  3:31                       ` Zhu Yanjun
2021-08-20  7:42                         ` yangx.jy
2021-08-20 21:40                           ` Bob Pearson
2021-08-20 22:09                             ` Bob Pearson
2021-08-13 21:53         ` Bob Pearson
2021-08-14  5:32           ` Leon Romanovsky
2021-08-23  7:53 ` Zhu Yanjun [this message]

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='CAD=hENdad8RGTLo82UBf3k+koQVX1oHSXMz6HfRvUxrL4dttsw@mail.gmail.com' \
    --to=zyjzyj2000@gmail.com \
    --cc=aglo@umich.edu \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@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;
as well as URLs for NNTP newsgroup(s).