From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Logan Gunthorpe'" <logang@deltatee.com>,
"'Arjun Vynipadath'" <arjun@chelsio.com>
Cc: "'Casey Leedom'" <leedom@chelsio.com>,
"'Sagi Grimberg'" <sagi@grimberg.me>, <netdev@vger.kernel.org>,
<linux-nvme@lists.infradead.org>,
"'Stephen Bates'" <sbates@raithlin.com>,
"'Ganesh Goudar'" <ganeshgr@chelsio.com>,
"'David S. Miller'" <davem@davemloft.net>,
"'Manoj Kumar Malviya'" <manojmalviya@chelsio.com>
Subject: RE: nvmet with cxgb4 is broken in v4.12-rc1
Date: Wed, 17 May 2017 14:22:23 -0500 [thread overview]
Message-ID: <046701d2cf42$e918bf30$bb4a3d90$@opengridcomputing.com> (raw)
In-Reply-To: <66da3b58-f722-28f0-1ed9-70f1e47276a4@deltatee.com>
> Hello,
>
> Another cxgb4 bug report for you. Testing nvmet over our T62100-LP-CR
> stopped working in v4.12-rc1. We are seeing two oopses: a general
> protection fault in nvmet_rdma_free_rsps and a WQ_MEM_RECLAIM warning.
> These occur after a suspect cxgb4 message. Please see the full dmesg log
> which is attached.
>
> > [ 41.093555] cxgb4 0000:07:00.4: AE qpid 1034 opcode 0 status 0x1 type 1 len
> 0x0 wrid.hi 0x0 wrid.lo 0x0
> > [ 41.093673] nvmet_rdma: received IB QP event: QP access error (3)
>
> I've bisected to find this commit is the culprit:
>
> bb58d079: cxgb4: Update IngPad and IngPack values
>
> A bisect log is also attached. Reverting that commit also fixes the issue.
>
Hey Logan, this is with 1.16.43.0 firmware?
Hey Casey/Manoj, is there some other sw or fw change missing for the ingpad change? Or maybe something needed in the firmware config file?
Thanks,
Steve.
next prev parent reply other threads:[~2017-05-17 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:38 BUG: nvmet with cxgb4 is broken in v4.12-rc1 Logan Gunthorpe
2017-05-17 19:22 ` Steve Wise [this message]
2017-05-17 19:23 ` Logan Gunthorpe
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='046701d2cf42$e918bf30$bb4a3d90$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=arjun@chelsio.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=manojmalviya@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=sbates@raithlin.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).