From: Kishon Vijay Abraham I <kishon@ti.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: pci-usb/pci-sata broken with LPAE config after "reduce use of block bounce buffers"
Date: Wed, 5 Feb 2020 14:02:51 +0530 [thread overview]
Message-ID: <4a8bf1d3-6f8e-d13e-eae0-4db54f5cab8c@ti.com> (raw)
In-Reply-To: <20200205074719.GA22701@lst.de>
Christoph,
On 05/02/20 1:17 PM, Christoph Hellwig wrote:
> On Wed, Feb 05, 2020 at 10:45:24AM +0530, Kishon Vijay Abraham I wrote:
>>> Ok, this mostly like means we allocate a swiotlb buffer that isn't
>>> actually addressable. To verify that can you post the output with the
>>> first attached patch? If it shows the overflow message added there,
>>> please try if the second patch fixes it.
>>
>> I'm seeing some sort of busy loop after applying your 1st patch. I sent
>> a SysRq to see where it is stuck
>
> And that shows up just with the patch? Really strange as it doesn't
> change any blockig points. What also is strange is that I don't see
> any of the warnings that should be there. FYI, the slightly updated
> version of the patch that went through my testing it here:
>
> git://git.infradead.org/users/hch/misc.git swiotlb-debug
>
> Gitweb:
>
> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/swiotlb-debug
>
> this also includes what was the second patch in the previous mail. Can
> you try that branch?
I see data mismatch with that branch.
Kernel log: https://pastebin.ubuntu.com/p/9g9cm7GzRh/
Kernel Config: https://pastebin.ubuntu.com/p/gYfpRDdVry/
Repo: https://github.com/kishon/linux-wip.git swiotlb-debug (Added an
additional patch for fixing a interrupt issue over your branch).
Thanks
Kishon
next prev parent reply other threads:[~2020-02-05 8:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 10:59 pci-usb/pci-sata broken with LPAE config after "reduce use of block bounce buffers" Kishon Vijay Abraham I
2019-11-15 13:06 ` Christoph Hellwig
2019-11-15 14:18 ` Kishon Vijay Abraham I
2019-11-16 16:35 ` Christoph Hellwig
2019-11-18 17:21 ` Robin Murphy
2019-11-25 5:43 ` Kishon Vijay Abraham I
2020-01-27 13:10 ` Kishon Vijay Abraham I
2020-01-27 13:22 ` Robin Murphy
2020-01-29 6:24 ` Kishon Vijay Abraham I
2020-01-30 7:58 ` Christoph Hellwig
2020-01-30 8:09 ` Kishon Vijay Abraham I
2020-01-30 16:42 ` Christoph Hellwig
2020-01-31 11:44 ` Kishon Vijay Abraham I
2020-02-03 14:21 ` Christoph Hellwig
2020-02-05 5:15 ` Kishon Vijay Abraham I
2020-02-05 7:47 ` Christoph Hellwig
2020-02-05 8:32 ` Kishon Vijay Abraham I [this message]
2020-02-05 8:48 ` Christoph Hellwig
2020-02-05 9:18 ` Kishon Vijay Abraham I
2020-02-05 9:19 ` Christoph Hellwig
2020-02-05 9:33 ` Kishon Vijay Abraham I
2020-02-05 16:05 ` Christoph Hellwig
2020-02-17 14:23 ` Christoph Hellwig
2020-02-18 12:15 ` Kishon Vijay Abraham I
2020-04-02 12:01 ` Kishon Vijay Abraham I
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=4a8bf1d3-6f8e-d13e-eae0-4db54f5cab8c@ti.com \
--to=kishon@ti.com \
--cc=hch@lst.de \
--cc=linux-pci@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).