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 11:33:35 +0800 [thread overview]
Message-ID: <54CC4D0F.9040805@huawei.com> (raw)
In-Reply-To: <54CB609D.60905@arm.com>
On 2015-01-30 18:44, Robin Murphy wrote:
> Hi Kefeng,
>
> On 30/01/15 10:19, Kefeng Wang wrote:
>> +cc linux-arm-kernel at lists.infradead.org
>>
>> On 2015-01-30 18:08, Kefeng Wang wrote:
>>> Hi all,
>>>
>>> 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
>>> ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>>> ata6.00: failed command: WRITE DMA EXT
>>> ata6.00: cmd 35/00:0f:05:0d:00/00:38:00:00:00/e0 tag 7 dma 7347712 out
>>> res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x40 (internal error)
>>> ata6.00: status: { DRDY }
>>> ata6.00: configured for UDMA/133
>>> ata6: EH complete
>>> -------------------------------------------------------------------------------
>>>
>>> It's difficult for us to git bisect, could anyone give us some advise, and idea?
>>>
>
> If it's not just a case of trying to map bigger buffers than SWIOTLB can bounce, you might be hitting the problem that this patch fixes:
>
> http://thread.gmane.org/gmane.linux.kernel/1853766
Hi, thanks for the response, tried, errors still exist.
>
>
> Robin.
>
>
> .
>
next prev parent reply other threads:[~2015-01-31 3:33 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 [this message]
2015-01-30 11:59 ` Catalin Marinas
2015-01-31 4:00 ` Kefeng Wang
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=54CC4D0F.9040805@huawei.com \
--to=wangkefeng.wang@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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