From: yizhan@redhat.com (Yi Zhang)
Subject: iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA
Date: Sat, 22 Apr 2017 04:09:57 -0400 (EDT) [thread overview]
Message-ID: <770183667.36997.1492848597368.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1613368219.36836.1492847910707.JavaMail.zimbra@redhat.com>
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>
next parent reply other threads:[~2017-04-22 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1613368219.36836.1492847910707.JavaMail.zimbra@redhat.com>
2017-04-22 8:09 ` Yi Zhang [this message]
2017-04-24 15:58 ` iwpm_register_pid: Unable to send a nlmsg (client = 2) observed on 4.11.0-rc7 during configure NVMe over iWARP RDMA Steve Wise
2017-04-24 16:07 ` Yi Zhang
2017-04-24 16:37 ` Steve Wise
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=770183667.36997.1492848597368.JavaMail.zimbra@redhat.com \
--to=yizhan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox