linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Zhang <markz@mellanox.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, oulijun <oulijun@huawei.com>,
	Parav Pandit <parav@mellanox.com>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: 【Ask for help】 A question for __ib_cache_gid_add()
Date: Fri, 1 Nov 2019 13:36:12 +0000	[thread overview]
Message-ID: <5d1c9c3d-6e28-0977-f02a-8224e40ae233@mellanox.com> (raw)
In-Reply-To: <f16f1832-6ca2-e606-259e-d039e8e47804@mellanox.com>

On 11/1/2019 9:21 PM, Mark Zhang wrote:
> On 11/1/2019 9:05 PM, Jason Gunthorpe wrote:
>> On Fri, Nov 01, 2019 at 05:36:36PM +0800, oulijun wrote:
>>> Hi
>>>     I am using the ubuntu system(5.0.0 kernel) to test the hip08 NIC port,. When I modify the perr mac1 to mac2,then restore to mac1, it will cause
>>> the gid0 and gid 1 of the roce to be unavailable, and check that the /sys/class/infiniband/hns_0/ports/1/gid_attrs/ndevs/0 is show invalid.
>>> the protocol stack print will appear.
>>>
>>>     Oct 16 17:59:36 ubuntu kernel: [200635.496317] __ib_cache_gid_add: unable to add gid fe80:0000:0000:0000:4600:4dff:fea7:9599 error=-28
>>> Oct 16 17:59:37 ubuntu kernel: [200636.705848] 8021q: adding VLAN 0 to HW filter on device enp189s0f0
>>> Oct 16 17:59:37 ubuntu kernel: [200636.705854] __ib_cache_gid_add: unable to add gid fe80:0000:0000:0000:4600:4dff:fea7:9599 error=-28
>>> Oct 16 17:59:39 ubuntu kernel: [200638.755828] hns3 0000:bd:00.0 enp189s0f0: link up
>>> Oct 16 17:59:39 ubuntu kernel: [200638.755847] IPv6: ADDRCONF(NETDEV_CHANGE): enp189s0f0: link becomes ready
>>> Oct 16 18:00:56 ubuntu kernel: [200715.699961] hns3 0000:bd:00.0 enp189s0f0: link down
>>> Oct 16 18:00:56 ubuntu kernel: [200716.016142] __ib_cache_gid_add: unable to add gid fe80:0000:0000:0000:4600:4dff:fea7:95f4 error=-28
>>> Oct 16 18:00:58 ubuntu kernel: [200717.229857] 8021q: adding VLAN 0 to HW filter on device enp189s0f0
>>> Oct 16 18:00:58 ubuntu kernel: [200717.229863] __ib_cache_gid_add: unable to add gid fe80:0000:0000:0000:4600:4dff:fea7:95f4 error=-28
>>>
>>> Has anyone else encounterd a similar problem ? I wonder if the _ib_cache_add_gid() is defective in 5.0 kernel?
>>
>> Maybe Parav knows?
>>
> One possibility is, during the operation you have port reset; Then
> all gids will be deleted and re-created. But during gids re-build
> gid entry #0 and #1 is in use, so they cannot be deleted then you
> get this error.
> 
I mean then you get this error message, which is expected. Check
all valid gid entries before and after the operation.

>> Jason
>>
> 


  reply	other threads:[~2019-11-01 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01  9:36 【Ask for help】 A question for __ib_cache_gid_add() oulijun
2019-11-01 13:05 ` Jason Gunthorpe
2019-11-01 13:21   ` Mark Zhang
2019-11-01 13:36     ` Mark Zhang [this message]
2019-11-05  8:47     ` oulijun
2019-11-01 16:00   ` Parav Pandit
2019-11-13 12:35     ` oulijun
2019-11-13 18:03       ` Parav Pandit

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=5d1c9c3d-6e28-0977-f02a-8224e40ae233@mellanox.com \
    --to=markz@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=oulijun@huawei.com \
    --cc=parav@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;
as well as URLs for NNTP newsgroup(s).