Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>, linux-rdma@vger.kernel.org
Subject: Re: srp/002 hang in blktests
Date: Mon, 23 Oct 2023 11:18:06 -0700	[thread overview]
Message-ID: <06229821-6d93-4f74-95ef-af352f101b7f@acm.org> (raw)
In-Reply-To: <b549a186-9c80-47e7-a54c-cd64d8cae9b7@gmail.com>


On 10/20/23 15:48, Bob Pearson wrote:
> Latest efforts. I completely reinstalled my machine. New Ubuntu 23.10 
> including multipath-tools-0.9.4-5ubuntu3, new rdma-linux git clone, new 
> blktests clone, etc. (Lost lots of Thunderbird state.) Ran srp/002 a few 
> times. It still hung on the third try. The dmsetup hack you sent still 
> un-hangs the stuck run.

Hi Bob,

Thanks for the detailed report. I installed Ubuntu 23.10 server into a
new VM and also all packages that are needed to build the kernel and run
blktests. This is how I ran the srp/002 test:

# (cd .../blktests && i=0 && while true; do ((i++)); echo ==== $i; 
./check srp/002; done)

With kernel v6.5-rc7, 40 iterations ran fine without triggering any
hang. I haven't found any kernel commits between v6.5-rc3 and v6.5-rc7
that could explain a behavior change for the SRP tests so I'm not sure
why we are seeing different results on our test setups ...

Thanks,

Bart.

  reply	other threads:[~2023-10-23 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 22:48 srp/002 hang in blktests Bob Pearson
2023-10-23 18:18 ` Bart Van Assche [this message]
2023-10-23 18:29   ` Bob Pearson
2023-10-23 20:21     ` Bart Van Assche
2023-10-23 20:41       ` Bob Pearson
2023-10-23 20:59         ` Bart Van Assche
2023-10-24 16:31           ` Bart Van Assche
2023-10-24 17:05             ` Bob Pearson

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=06229821-6d93-4f74-95ef-af352f101b7f@acm.org \
    --to=bvanassche@acm.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