From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>,
linux-rdma@vger.kernel.org, jgg@nvidia.com
Subject: Re: srp/002 hang in blktests
Date: Tue, 24 Oct 2023 09:31:19 -0700 [thread overview]
Message-ID: <119304fc-a61d-4567-8d23-edb69676fad5@acm.org> (raw)
In-Reply-To: <f561804c-41c8-48af-ab2b-45f54bd117b6@acm.org>
On 10/23/23 13:59, Bart Van Assche wrote:
> On 10/23/23 13:41, Bob Pearson wrote:
>> On 10/23/23 15:21, Bart Van Assche wrote:
>>> On 10/23/23 11:29, Bob Pearson wrote:
>>>> Lots of work. Thanks!! Did you mean 6.6 instead of 6.5? I assume
>>>> you are running an Ubuntu 23.10 VM and not bare metal while I am
>>>> not.
>>>
>>> Yes, I meant 6.6 instead of 6.5. I'm indeed running Ubuntu 23.10
>>> inside a VM. BTW, the test is still running and has just reached 231
>>> iterations
>>> ...
>>
>> Very good news! Maybe we can let rxe out of the doghouse.
>
> Is there perhaps a misunderstanding? I ran my tests with the soft-iWARP
> driver. Did you run your tests with the RXE driver?
(replying to my own email)
With the RXE driver I see a hang after 143 iterations in the same VM
(Ubuntu 23.10 VM, v6.6-rc7 kernel with kernel debugging disabled). No
SRP paths are available so the hang is not caused by a multipathd bug:
# lsscsi
[0:0:0:0] cd/dvd QEMU QEMU DVD-ROM 2.5+ /dev/sr0
[6:0:0:0] disk Linux scsi_debug 0191 /dev/sda
I couldn't obtain more information because kernel debugging is disabled.
But it is suspicious that this hang happens with the RXE driver and not
with the soft-iWARP driver.
Bart.
next prev parent reply other threads:[~2023-10-24 16:31 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
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 [this message]
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=119304fc-a61d-4567-8d23-edb69676fad5@acm.org \
--to=bvanassche@acm.org \
--cc=jgg@nvidia.com \
--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