Robert Hancock wrote: > Tejun Heo wrote: >> Juergen Kreileder wrote: >>> 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. >> Hmm... sounds like mapping is leaking. Eh... iommu leak debug seems to >> support only AMD GART IOMMU. How long does it take to reproduce the >> bug? Once it happens, it never recovers, right? Does the problem >> happen with minimal configuration w/ only libata enabled (no network, no >> sound, no usb...)? > > Yes, that would be a good test.. Easiest way might be booting with > init=/bin/sh and running some processes that do lots of disk access.. After a bit more testing I'm pretty sure the problem is caused by an external driver, namely the new ath9k driver. Sorry for the noise on the wrong lists. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://blog.blackdown.de/ -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html