So, for me this bug is caused by some change between 2.6.18 and
2.6.18.8, but going through the changelogs I can see no point that
should cause this...
Maybe this should go to the kernel developers.
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Moritz
Möller
Sent: Thursday, March 20, 2008 12:57 PM
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] 3w-9xxx / Out of SW_IOMMU space
Hi,
i''ve seen some posts regarding this, and wanted to tell you what I have
found out so far.
Xen 3.2 with 2.8.18.8 kernel from xen (linux-2.6.18-xen.hg) gives lot of
SW IOMMU errors after a 2-3 GB on-disk copy on a 3ware controller.
If I use the older kernel that we used with Xen 3.1 together with the
new xen 3.2 hypervisor, I see no problems.
Both kernels were compiled using the same 3w-9xxx.c, so it has to be
caused by something in the kernel. I''m currently rebuilding the
2.8.18.8
that comes with xen 3.1 to verify this.
Moritz
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel