iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

[Yi Zhang]

Hello experts

I found below pid_query_error, could anyone help check it? I have attached all the dmesg log. Thanks

[  152.372481] nvmet: adding nsid 1 to subsystem testnqn
[  152.398705] iwpm_register_pid: Unable to send a nlmsg (client = 2)
[  152.430011] nvmet_rdma: enabling port 2 (172.31.52.12:4420)


Best Regards,
  Yi Zhang


-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.log
Type: text/x-log
Size: 65341 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20170422/92671ff3/attachment-0001.bin>

iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

[Steve Wise]

> Subject: iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-
> rc7 during configure NVMe over iWARP RDMA
> 
> Hello experts
> 
> I found below pid_query_error, could anyone help check it? I have attached all the
> dmesg log. Thanks
> 
> [  152.372481] nvmet: adding nsid 1 to subsystem testnqn
> [  152.398705] iwpm_register_pid: Unable to send a nlmsg (client = 2)
> [  152.430011] nvmet_rdma: enabling port 2 (172.31.52.12:4420)
> 
> 
> Best Regards,
>   Yi Zhang
>

Hey Yi, 

This is the iWARP port mapping kernel service logging that no iwarp port mapper daemon is running on the system.  This is benign in the context of nvme/fabrics.  Are you having other problems with using iw_cxgb4?

Steve.
 

iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

[Yi Zhang]

Hi Steve

Here is another issue I filed that using iw_cxgb4. 
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009458.html

Best Regards,
  Yi Zhang


----- Original Message -----
From: "Steve Wise" <swise@opengridcomputing.com>
To: "Yi Zhang" <yizhan at redhat.com>, linux-nvme at lists.infradead.org, linux-rdma at vger.kernel.org
Sent: Monday, April 24, 2017 11:58:48 PM
Subject: RE: iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

> Subject: iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-
> rc7 during configure NVMe over iWARP RDMA
> 
> Hello experts
> 
> I found below pid_query_error, could anyone help check it? I have attached all the
> dmesg log. Thanks
> 
> [  152.372481] nvmet: adding nsid 1 to subsystem testnqn
> [  152.398705] iwpm_register_pid: Unable to send a nlmsg (client = 2)
> [  152.430011] nvmet_rdma: enabling port 2 (172.31.52.12:4420)
> 
> 
> Best Regards,
>   Yi Zhang
>

Hey Yi, 

This is the iWARP port mapping kernel service logging that no iwarp port mapper daemon is running on the system.  This is benign in the context of nvme/fabrics.  Are you having other problems with using iw_cxgb4?

Steve.
 

iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA

[Steve Wise]

> 
> Hi Steve
> 
> Here is another issue I filed that using iw_cxgb4.
> http://lists.infradead.org/pipermail/linux-nvme/2017-April/009458.html
> 
> Best Regards,
>   Yi Zhang

Oh ok.

Chelsio will have a look at this asap.  

Thanks,

Steve.