From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: v5.14 RXE driver broken?
Date: Wed, 25 Aug 2021 14:44:19 -0700 [thread overview]
Message-ID: <f436017c-fa40-3e62-8f75-94ea01f36127@acm.org> (raw)
In-Reply-To: <c4550410-5b5a-b460-c57c-af2008b5c0e9@gmail.com>
On 8/25/21 2:09 PM, Bob Pearson wrote:
> Are you seeing the ib_alloc_mr() failure in 5.14? I thought that was just a
> 5.13 thing. I am still not seeing that error in my test setup. I am getting > a soft lockup error after ~20 seconds. During most of that there is a> constant exchange of req/ack packets with nothing else happening.
>
> If you want I can send you a patch to print out error messages from MR
> allocation.
Hi Bob,
I see the ib_alloc_mr() failures with kernel v5.14 in two different VMs. A
different Linux distro has been installed in each VM.
If it would help your debugging efforts, please send me the patch that prints
out the MR allocation error messages.
Bart.
next prev parent reply other threads:[~2021-08-25 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 3:01 v5.14 RXE driver broken? Bart Van Assche
2021-08-25 3:02 ` Zhu Yanjun
2021-08-25 16:32 ` Jason Gunthorpe
2021-08-25 18:03 ` Bob Pearson
2021-08-25 18:22 ` Bart Van Assche
2021-08-25 20:58 ` Bart Van Assche
2021-08-25 21:09 ` Bob Pearson
2021-08-25 21:44 ` Bart Van Assche [this message]
2021-08-26 19:03 ` Bob Pearson
2021-08-26 20:03 ` Bob Pearson
2021-08-27 3:18 ` Zhu Yanjun
2021-08-25 16:46 ` Bart Van Assche
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=f436017c-fa40-3e62-8f75-94ea01f36127@acm.org \
--to=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=linux-block@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.