[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <66da3b58-f722-28f0-1ed9-70f1e47276a4@deltatee.com>
Date: Wed, 17 May 2017 11:38:46 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Arjun Vynipadath <arjun@...lsio.com>
Cc: Casey Leedom <leedom@...lsio.com>,
Ganesh Goudar <ganeshgr@...lsio.com>,
"David S. Miller" <davem@...emloft.net>,
Stephen Bates <sbates@...thlin.com>,
SWise OGC <swise@...ngridcomputing.com>,
netdev@...r.kernel.org, linux-nvme@...ts.infradead.org,
Sagi Grimberg <sagi@...mberg.me>
Subject: BUG: nvmet with cxgb4 is broken in v4.12-rc1
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.
Thanks,
Logan
View attachment "bisect.nvmet1.log" of type "text/x-log" (2866 bytes)
View attachment "dmesg.log" of type "text/x-log" (89642 bytes)
Powered by blists - more mailing lists