From: wangkefeng.wang@huawei.com (Kefeng Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: ask for help about swiotlb buffer is full
Date: Sat, 31 Jan 2015 12:00:06 +0800 [thread overview]
Message-ID: <54CC5346.5070402@huawei.com> (raw)
In-Reply-To: <20150130115915.GB27542@e104818-lin.cambridge.arm.com>
On 2015-01-30 19:59, Catalin Marinas wrote:
> On Fri, Jan 30, 2015 at 10:19:16AM +0000, Kefeng Wang wrote:
>> On 2015-01-30 18:08, Kefeng Wang wrote:
>>> There is an AHCI compliant SATA controller in our arm64 soc, and
>>> it only supports 32bit DMA(used coherent dma_ops). It works well
>>> in v3.16. Recently, we update kernel from linux v3.16 to linux
>>> v3.19-rc4(use defconfig in arm64), but we get errors when test
>>> sata driver, as follows.
>>>
>>> ------------------------------------------------------------------------------
>>> ahci b1002800.sata: swiotlb buffer is full (sz: 65536 bytes)
>>> DMA: Out of SW-IOMMU space for 65536 bytes at device b1002800.sata
>
> Do you use a 64KB page kernel configuration?
>
> What does your kernel log say about "software IO TLB [mem ...]"?
>
4kb page, use Make ARCH=arm64 defconfig in v3.19 to generate config.
[ 0.678293] software IO TLB [mem 0x7e800000-0x7ec00000] (4MB) mapped at [ffffffc07e800000-ffffffc07ebfffff]
[ 0.686991] DMA: preallocated 256 KiB pool for atomic allocations
next prev parent reply other threads:[~2015-01-31 4:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54CB5820.9020102@huawei.com>
2015-01-30 10:19 ` ask for help about swiotlb buffer is full Kefeng Wang
2015-01-30 10:44 ` Robin Murphy
2015-01-31 3:33 ` Kefeng Wang
2015-01-30 11:59 ` Catalin Marinas
2015-01-31 4:00 ` Kefeng Wang [this message]
2015-02-02 18:24 ` Catalin Marinas
2015-02-04 12:01 ` Kefeng Wang
2015-02-04 13:32 ` Catalin Marinas
2015-02-04 14:48 ` Ding Tianhong
2015-02-05 18:19 ` Catalin Marinas
2015-02-07 1:53 ` Kefeng Wang
2015-02-09 16:50 ` Catalin Marinas
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=54CC5346.5070402@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.