From: "Marciniszyn, Mike" <mike.marciniszyn@cornelisnetworks.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: NFS dmesg errors in 5.14-rc1
Date: Wed, 14 Jul 2021 16:40:35 +0000 [thread overview]
Message-ID: <CH0PR01MB7153D36F6E35AF2239C763C0F2139@CH0PR01MB7153.prod.exchangelabs.com> (raw)
Chuck,
We are now seeing this in the first RC:
[31868.644165] ------------[ cut here ]------------
[31868.650059] failed to drain recv queue: -22
[31868.655191] WARNING: CPU: 32 PID: 559 at drivers/infiniband/core/verbs.c:2738 __ib_drain_rq+0x163/0x1a0 [ib_core]
[31868.657234] ------------[ cut here ]------------
[31868.667133] Modules linked in: nfsv3
[31868.672832] failed to drain send queue: -22
[31868.677279] nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs tcp_diag udp_diag raw_diag inet_diag rfkill ib_isert iscsi_target_mod target_core_mod rpcrdma ib_iser rdma_ucm opa_vnic rdma_cm ib_umad libiscsi ib_ipoib scsi_transport_iscsi ib_cm iw_cm sunrpc hfi1 mgag200 intel_rapl_msr intel_rapl_common drm_kms_helper sb_edac syscopyarea rdmavt x86_pkg_temp_thermal sysfillrect intel_powerclamp ipmi_si ib_uverbs sysimgblt coretemp fb_sys_fops cec ipmi_devintf drm crct10dif_pclmul crc32_pclmul iTCO_wdt iTCO_vendor_support ghash_clmulni_intel ib_core mei_me rapl intel_cstate mei lpc_ich mxm_wmi i2c_i801
[31868.682425] WARNING: CPU: 65 PID: 608575 at drivers/infiniband/core/verbs.c:2705 __ib_drain_sq+0x14d/0x190 [ib_core]
On the same tests, the mount command fails with a connection refused...
Any ideas on this?
5.13.1 (the first 5.13.y release) tests fine.
Mike
next reply other threads:[~2021-07-14 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:40 Marciniszyn, Mike [this message]
2021-07-14 19:43 ` NFS dmesg errors in 5.14-rc1 Chuck Lever III
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=CH0PR01MB7153D36F6E35AF2239C763C0F2139@CH0PR01MB7153.prod.exchangelabs.com \
--to=mike.marciniszyn@cornelisnetworks.com \
--cc=chuck.lever@oracle.com \
--cc=linux-rdma@vger.kernel.org \
/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).