From: Juergen Kreileder <jk@blackdown.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: SW-IOMMU / ata_piix errors with 2.6.27-rc1
Date: Mon, 04 Aug 2008 02:40:46 +0200 [thread overview]
Message-ID: <4896500E.2040304@blackdown.de> (raw)
In-Reply-To: <4896157A.2020907@shaw.ca>
Robert Hancock wrote:
> Juergen Kreileder wrote:
>> Hi,
>>
>> I get lots of errors like this with 2.6.27-rc1 on my
>> Macbook Pro (3rd generation), 2.6.26 seems to work fine:
>>
>> [ 907.524509] DMA: Out of SW-IOMMU space for 45056 bytes at device 0000:00:1f.2
>> [ 907.524783] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> [ 907.524796] ata3.00: cmd 35/00:50:08:91:5c/00:01:0f:00:00/e0 tag 0 dma 172032 out
>> [ 907.524798] res 50/00:00:ff:90:5c/00:00:0f:00:00/ef Emask 0x40 (internal error)
>> [ 907.524805] ata3.00: status: { DRDY }
>> [ 907.646590] ata3.00: configured for UDMA/133
>> [ 907.646624] ata3: EH complete
>>
>>
>> Any suggestions?
>
> You can try increasing the swiotlb size by booting with swiotlb=65536
> (for 128MB) or swiotlb=131072 (for 256MB), and see if that makes the
> problem go away.. It's unclear why you'd be running out of SWIOTLB space
> now, though, if 2.6.26 worked fine..
Still happening, although 256M make it a bit harder to trigger.
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://blog.blackdown.de/
next prev parent reply other threads:[~2008-08-04 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.64b92XSd5HpCdpOYcDENnJSZJyw@ifi.uio.no>
2008-08-03 20:30 ` SW-IOMMU / ata_piix errors with 2.6.27-rc1 Robert Hancock
2008-08-04 0:40 ` Juergen Kreileder [this message]
2008-08-04 2:19 ` Tejun Heo
2008-08-04 2:47 ` Robert Hancock
2008-08-04 22:09 ` Running out of SWIOTLB space (was: SW-IOMMU / ata_piix errors with 2.6.27-rc1) Juergen Kreileder
2008-08-03 17:10 SW-IOMMU / ata_piix errors with 2.6.27-rc1 Juergen Kreileder
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=4896500E.2040304@blackdown.de \
--to=jk@blackdown.de \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).