From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will@kernel.org>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org,
Alexey Dobriyan <adobriyan@gmail.com>,
axboe@fb.com, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme-pci: slimmer CQ head update
Date: Thu, 7 May 2020 14:55:37 +0100 [thread overview]
Message-ID: <e1643b53-d362-0b5e-573f-72f0ea249ebf@huawei.com> (raw)
In-Reply-To: <4dae5990-e81b-8b33-dafc-ee47e4f06b6a@arm.com>
On 07/05/2020 12:04, Robin Murphy wrote:
>> [ 177.132810] DMA-API: nvme 0000:85:00.0: device driver tries to free
>> DMA memor
>> y it has not allocated [device address=0x00000000ef371000] [size=4096
>> bytes]
> [...]
>> [ 177.276322] debug_dma_unmap_page+0x6c/0x78
>> [ 177.280487] nvme_unmap_data+0x7c/0x23c
>> [ 177.284305] nvme_pci_complete_rq+0x28/0x58
>
> OK, so there's clearly something amiss there. I would have suggested
> next sticking the SMMU in passthrough to help focus on the DMA API
> debugging, but since that "DMA address" looks suspiciously like a
> physical address rather than an IOVA, I suspect that things might
> suddenly appear to be working fine if you do...
OK, seems sensible. However it looks like this guy triggers the issue:
324b494c2862 nvme-pci: Remove two-pass completions
With carrying the revert of $subject, it's a quick bisect to that patch.
I always get the RCU cpu stall warning, which obscures thing a bit.
Cheers,
John
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-05-07 13:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 18:45 [PATCH] nvme-pci: slimmer CQ head update Alexey Dobriyan
2020-02-29 5:53 ` Keith Busch
2020-05-06 11:03 ` John Garry
2020-05-06 12:47 ` Keith Busch
2020-05-06 13:24 ` Alexey Dobriyan
2020-05-06 13:44 ` John Garry
2020-05-06 14:01 ` Alexey Dobriyan
2020-05-06 14:35 ` Christoph Hellwig
2020-05-06 16:26 ` John Garry
2020-05-06 16:31 ` Will Deacon
2020-05-06 16:52 ` Robin Murphy
2020-05-06 17:02 ` John Garry
2020-05-07 8:18 ` John Garry
2020-05-07 11:04 ` Robin Murphy
2020-05-07 13:55 ` John Garry [this message]
2020-05-07 14:23 ` Keith Busch
2020-05-07 15:11 ` John Garry
2020-05-07 15:35 ` Keith Busch
2020-05-07 15:41 ` John Garry
2020-05-08 16:16 ` Keith Busch
2020-05-08 17:04 ` John Garry
2020-05-07 16:26 ` Robin Murphy
2020-05-07 17:35 ` Keith Busch
2020-05-07 17:44 ` Will Deacon
2020-05-07 18:06 ` Keith Busch
2020-05-08 11:40 ` Will Deacon
2020-05-08 14:07 ` Keith Busch
2020-05-08 15:34 ` Keith Busch
2020-05-06 14:44 ` Keith Busch
2020-05-07 15:58 ` Keith Busch
2020-05-07 20:07 ` [PATCH] nvme-pci: fix "slimmer CQ head update" Alexey Dobriyan
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=e1643b53-d362-0b5e-573f-72f0ea249ebf@huawei.com \
--to=john.garry@huawei.com \
--cc=adobriyan@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=sagi@grimberg.me \
--cc=will@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