linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Bernard Metzler <bmt@zurich.ibm.com>,
	Zhu Yanjun <zyjzyj2000@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: Yi Zhang <yi.zhang@redhat.com>, Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: Apparent regression in blktests since 5.18-rc1+
Date: Tue, 17 May 2022 22:44:54 +0200	[thread overview]
Message-ID: <88e9b45d-e7cd-45ce-ad12-d1ec8e238bc8@acm.org> (raw)
In-Reply-To: <ad81fbce-0b8c-c49f-00d5-c8c2678a5779@gmail.com>

On 5/17/22 17:21, Bob Pearson wrote:
> Thanks Bart. I was able to follow your steps above. But unfortunately not much has changed.
> I still see hangs in siw (with no code changes by me) and also in rxe (but here I have
> fixed some lockdep warnings so it will run in a debug kernel.) There are two test cases that
> cause the most problems. srp/002 and srp/011. 011 always fails solidly. 002 sometimes hangs and
> sometimes completes but with failed status. The rest of the tests all pass.
> 
> Both tests hang at a line that looks like
> 	scsi host6: ib_srp: Already connected to target port with id_ext=...
> 
> When 002 completes but fails there are 14 second gaps at some of the same lines in the trace.
> This has the feel of the earlier problem with the 3 minute timeout that was fixed by the
> patch (revert ... scsi_debug.c) that you sent and is applied here.
> 
> I really don't know how to make progress here. If anyone knows what is happening at the
> already connected lines let me know. They seem normal except for the long gaps and hangs
> when they occur.

How about sharing the kernel config file that you are using in your 
tests such that I can try to reproduce the behavior that you are observing?

Thanks,

Bart.

  reply	other threads:[~2022-05-17 20:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 18:11 Bob Pearson
2022-05-07  0:10 ` Bart Van Assche
2022-05-07  0:29   ` Yanjun Zhu
2022-05-07  1:29     ` Jason Gunthorpe
2022-05-07  1:55       ` Yanjun Zhu
2022-05-07 13:43         ` Bob Pearson
2022-05-08  4:13           ` Bart Van Assche
2022-05-10 15:24             ` Pearson, Robert B
2022-05-12 21:57             ` Bob Pearson
2022-05-12 22:25               ` Bart Van Assche
2022-05-13  0:41                 ` Bob Pearson
2022-05-13  3:40                   ` Bart Van Assche
2022-05-17 15:21                     ` Bob Pearson
2022-05-17 20:44                       ` Bart Van Assche [this message]
2022-05-17 20:54                         ` Bob Pearson
2022-05-17 20:59                         ` Bob Pearson
2022-05-08  8:43         ` Yanjun Zhu
2022-05-09  8:01       ` Zhu Yanjun
2022-05-09 11:52         ` Jason Gunthorpe
2022-05-09 12:31           ` Yanjun Zhu
2022-05-09 12:33             ` Jason Gunthorpe
2022-05-09 12:42               ` Yanjun Zhu
2022-05-07 13:40     ` Bob Pearson
2022-05-09  6:56 ` Thorsten Leemhuis
2022-05-10  3:53   ` 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=88e9b45d-e7cd-45ce-ad12-d1ec8e238bc8@acm.org \
    --to=bvanassche@acm.org \
    --cc=bmt@zurich.ibm.com \
    --cc=dgilbert@interlog.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yi.zhang@redhat.com \
    --cc=zyjzyj2000@gmail.com \
    --subject='Re: Apparent regression in blktests since 5.18-rc1+' \
    /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

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).