This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Massive problems with 'PCI-DMA: Out of SW-IOMMU spac

To: Markus Schuster <ma.schuster@xxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Massive problems with 'PCI-DMA: Out of SW-IOMMU space for XXX bytes [..]' with 3Ware controller
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 28 Jan 2008 21:58:35 +0000
Delivery-date: Mon, 28 Jan 2008 13:58:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <fnlhmc$6ja$1@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Achh+O3ULEWiWs3sEdy39QAWy6hiGQ==
Thread-topic: [Xen-devel] Re: Massive problems with 'PCI-DMA: Out of SW-IOMMU space for XXX bytes [..]' with 3Ware controller
User-agent: Microsoft-Entourage/
On 28/1/08 21:33, "Markus Schuster" <ma.schuster@xxxxxx> wrote:

> Randy McAnally wrote:
>>> PCI-DMA: Out of SW-IOMMU space for 40960 bytes at device 0000:03:00.0
>>> 3w-9xxx: scsi0: ERROR: (0x06:0x001C): Failed to map scatter gather list.
>>> (03:00.0 is the 3Ware Controller)
>> Me too as well...any progress on this issue?
> I thought about writing to the mailing-list this days, too. Maybe there has
> been some fix in 3.2.0 or 3.1.3?
> Keir, do you have any news on this annoying issue?

No, except to say that it is almost certainly a dom0 kernel issue, not core
hypervisor. So it will not be fixed by just changing hypervisor version if
you retain the same dom0 kernel version. What kernel are you using? Have you
tried a vendor Xen kernel for your distro?

I think there have been reports of this problem with our 2.6.18-based
kernel, but noone has provided a patch to fix it as far as I know.

 -- Keir

Xen-devel mailing list