From: Sagi Grimberg <sagi@grimberg.me>
To: Yi Zhang <yi.zhang@redhat.com>, linux-nvme@lists.infradead.org
Cc: danielj@mellanox.com, parav@mellanox.com,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: regression: nvme rdma with bnxt_re0 broken
Date: Thu, 11 Jul 2019 09:13:41 -0700 [thread overview]
Message-ID: <648e86db-864f-9eb1-5275-564a1ef535fb@grimberg.me> (raw)
In-Reply-To: <619411460.27128070.1562838433020.JavaMail.zimbra@redhat.com>
CC linux-rdma
On 7/11/19 2:47 AM, Yi Zhang wrote:
> Hello
>
> 'nvme connect' failed when use bnxt_re0 on latest upstream build[1], by bisecting I found it was introduced from v5.2.0-rc1 with [2], it works after I revert it.
> Let me know if you need more info, thanks.
>
> [1]
> [root@rdma-perf-07 ~]$ nvme connect -t rdma -a 172.31.40.125 -s 4420 -n testnqn
> Failed to write to /dev/nvme-fabrics: Bad address
>
> [root@rdma-perf-07 ~]$ dmesg
> [ 476.320742] bnxt_en 0000:19:00.0: QPLIB: cmdq[0x4b9]=0x15 status 0x5
> [ 476.327103] infiniband bnxt_re0: Failed to allocate HW AH
> [ 476.332525] nvme nvme2: rdma_connect failed (-14).
> [ 476.343552] nvme nvme2: rdma connection establishment failed (-14)
>
> [root@rdma-perf-07 ~]$ lspci | grep -i Broadcom
> 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
> 01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
> 18:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)
> 19:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01)
> 19:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01)
>
>
> [2]
> commit 823b23da71132b80d9f41ab667c68b112455f3b6
> Author: Parav Pandit <parav@mellanox.com>
> Date: Wed Apr 10 11:23:03 2019 +0300
>
> IB/core: Allow vlan link local address based RoCE GIDs
>
> IPv6 link local address for a VLAN netdevice has nothing to do with its
> resemblance with the default GID, because VLAN link local GID is in
> different layer 2 domain.
>
> Now that RoCE MAD packet processing and route resolution consider the
> right GID index, there is no need for an unnecessary check which prevents
> the addition of vlan based IPv6 link local GIDs.
>
> Signed-off-by: Parav Pandit <parav@mellanox.com>
> Reviewed-by: Daniel Jurgens <danielj@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
>
>
>
> Best Regards,
> Yi Zhang
>
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: regression: nvme rdma with bnxt_re0 broken
Date: Thu, 11 Jul 2019 09:13:41 -0700 [thread overview]
Message-ID: <648e86db-864f-9eb1-5275-564a1ef535fb@grimberg.me> (raw)
In-Reply-To: <619411460.27128070.1562838433020.JavaMail.zimbra@redhat.com>
CC linux-rdma
On 7/11/19 2:47 AM, Yi Zhang wrote:
> Hello
>
> 'nvme connect' failed when use bnxt_re0 on latest upstream build[1], by bisecting I found it was introduced from v5.2.0-rc1 with [2], it works after I revert it.
> Let me know if you need more info, thanks.
>
> [1]
> [root at rdma-perf-07 ~]$ nvme connect -t rdma -a 172.31.40.125 -s 4420 -n testnqn
> Failed to write to /dev/nvme-fabrics: Bad address
>
> [root at rdma-perf-07 ~]$ dmesg
> [ 476.320742] bnxt_en 0000:19:00.0: QPLIB: cmdq[0x4b9]=0x15 status 0x5
> [ 476.327103] infiniband bnxt_re0: Failed to allocate HW AH
> [ 476.332525] nvme nvme2: rdma_connect failed (-14).
> [ 476.343552] nvme nvme2: rdma connection establishment failed (-14)
>
> [root at rdma-perf-07 ~]$ lspci | grep -i Broadcom
> 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
> 01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
> 18:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)
> 19:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01)
> 19:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01)
>
>
> [2]
> commit 823b23da71132b80d9f41ab667c68b112455f3b6
> Author: Parav Pandit <parav at mellanox.com>
> Date: Wed Apr 10 11:23:03 2019 +0300
>
> IB/core: Allow vlan link local address based RoCE GIDs
>
> IPv6 link local address for a VLAN netdevice has nothing to do with its
> resemblance with the default GID, because VLAN link local GID is in
> different layer 2 domain.
>
> Now that RoCE MAD packet processing and route resolution consider the
> right GID index, there is no need for an unnecessary check which prevents
> the addition of vlan based IPv6 link local GIDs.
>
> Signed-off-by: Parav Pandit <parav at mellanox.com>
> Reviewed-by: Daniel Jurgens <danielj at mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro at mellanox.com>
> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com>
>
>
>
> Best Regards,
> Yi Zhang
>
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
next prev parent reply other threads:[~2019-07-11 16:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310083272.27124086.1562836112586.JavaMail.zimbra@redhat.com>
2019-07-11 9:47 ` regression: nvme rdma with bnxt_re0 broken Yi Zhang
2019-07-11 12:54 ` Parav Pandit
2019-07-11 16:18 ` Parav Pandit
2019-07-11 16:18 ` Parav Pandit
2019-07-12 1:53 ` Yi Zhang
2019-07-12 1:53 ` Yi Zhang
2019-07-12 2:49 ` Parav Pandit
2019-07-12 2:49 ` Parav Pandit
2019-07-12 3:45 ` Selvin Xavier
2019-07-12 3:45 ` Selvin Xavier
2019-07-12 9:28 ` Parav Pandit
2019-07-12 9:28 ` Parav Pandit
2019-07-12 9:39 ` Parav Pandit
2019-07-12 9:39 ` Parav Pandit
2019-07-12 9:49 ` Parav Pandit
2019-07-12 9:49 ` Parav Pandit
2019-07-12 11:41 ` Yi Zhang
2019-07-12 11:41 ` Yi Zhang
2019-07-12 12:52 ` Parav Pandit
2019-07-12 12:52 ` Parav Pandit
2019-07-12 15:40 ` Jason Gunthorpe
2019-07-12 15:40 ` Jason Gunthorpe
2019-07-12 16:29 ` Selvin Xavier
2019-07-12 16:29 ` Selvin Xavier
2019-07-12 17:42 ` Jason Gunthorpe
2019-07-12 17:42 ` Jason Gunthorpe
2019-07-13 7:51 ` Selvin Xavier
2019-07-13 7:51 ` Selvin Xavier
2019-07-13 12:12 ` Jason Gunthorpe
2019-07-13 12:12 ` Jason Gunthorpe
2019-07-12 16:18 ` Selvin Xavier
2019-07-12 16:18 ` Selvin Xavier
2019-07-13 7:56 ` Yi Zhang
2019-07-13 7:56 ` Yi Zhang
2019-07-13 16:00 ` Selvin Xavier
2019-07-13 16:00 ` Selvin Xavier
2019-07-11 16:13 ` Sagi Grimberg [this message]
2019-07-11 16:13 ` Sagi Grimberg
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=648e86db-864f-9eb1-5275-564a1ef535fb@grimberg.me \
--to=sagi@grimberg.me \
--cc=danielj@mellanox.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=yi.zhang@redhat.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.