From: maxg@mellanox.com (Max Gurtovoy)
Subject: [PATCH 1/3] nvme: rename NVME_CTRL_RECONNECTING state to NVME_CTRL_CONNECTING
Date: Wed, 14 Feb 2018 16:20:38 +0200 [thread overview]
Message-ID: <86130f62-dc14-e0d1-8e67-8918e4fcf59c@mellanox.com> (raw)
In-Reply-To: <44b5f866-3b98-ba25-ff8a-3c0ce9f03c8b@grimberg.me>
On 2/14/2018 3:40 PM, Sagi Grimberg wrote:
>
>> During port toggle with traffic (using dm-multipath) I see some
>> warnings during ib_destroy_qp that say there are still mrs_used.
>> and therefore also in ib_dealloc_pd that says refcount on pd is not 0.
>>
>> I'll debug it tomorrow hopefully and update.
>
> Is this a regression that happened due to your patch set?
I don't think so. Without my patches we crash.
I see that we have a timeout on admin_q, and then I/O error:
[Wed Feb 14 14:10:59 2018] nvme nvme0: I/O 0 QID 0 timeout, reset controller
[Wed Feb 14 14:10:59 2018] nvme nvme0: failed nvme_keep_alive_end_io
error=10
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 704258460
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 388820158
[Wed Feb 14 14:10:59 2018] ib_mr_pool_destroy: destroyed 121 mrs,
mrs_used 6 for qp 000000008182fc6f
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 489120554
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 399385206
[Wed Feb 14 14:10:59 2018] device-mapper: multipath: Failing path 259:0.
[Wed Feb 14 14:10:59 2018] WARNING: CPU: 9 PID: 12333 at
drivers/infiniband/core//verbs.c:1524 ib_destroy_qp+0x159/0x170 [ib_core]
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 269330912
[Wed Feb 14 14:10:59 2018] Modules linked in:
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 211936734
[Wed Feb 14 14:10:59 2018] nvme_rdma(OE)
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 383446442
[Wed Feb 14 14:10:59 2018] nvme_fabrics(OE) nvme_core(OE)
[Wed Feb 14 14:10:59 2018] print_req_error: I/O error, dev nvme0n1,
sector 160594228
for some reason not all commands complete before we destroy the QP (we
use dm-multipath here).
In iser (we also saw that the pool has registered regions) we created
all_list and we free the MRs from there...
-Max.
next prev parent reply other threads:[~2018-02-14 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:31 [PATCH v3 0/3] Fix host side state machine Max Gurtovoy
2018-01-31 16:31 ` [PATCH 1/3] nvme: rename NVME_CTRL_RECONNECTING state to NVME_CTRL_CONNECTING Max Gurtovoy
2018-01-31 17:10 ` James Smart
2018-02-08 15:28 ` Sagi Grimberg
2018-02-08 16:19 ` Sagi Grimberg
2018-02-13 10:19 ` Max Gurtovoy
2018-02-13 10:46 ` Sagi Grimberg
2018-02-13 18:01 ` Max Gurtovoy
2018-02-13 23:55 ` Max Gurtovoy
2018-02-14 13:40 ` Sagi Grimberg
2018-02-14 14:20 ` Max Gurtovoy [this message]
2018-02-15 18:09 ` Max Gurtovoy
2018-01-31 16:31 ` [PATCH 2/3] nvme-rdma: use NVME_CTRL_CONNECTING state to mark init process Max Gurtovoy
2018-01-31 17:10 ` James Smart
2018-01-31 16:31 ` [PATCH 3/3] nvme: delete NVME_CTRL_LIVE --> NVME_CTRL_CONNECTING transition Max Gurtovoy
2018-01-31 17:11 ` James Smart
2018-02-05 14:46 ` [PATCH v3 0/3] Fix host side state machine Sagi Grimberg
2018-02-06 15:01 ` Max Gurtovoy
2018-02-08 16:01 ` Keith Busch
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=86130f62-dc14-e0d1-8e67-8918e4fcf59c@mellanox.com \
--to=maxg@mellanox.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